On 2016-04-26, Branko Čibej wrote:
> Externals /are/ nested working copies as far as the client is concerned.
> Sure nothing prevents you from using nested working copies that aren't
> tracked as externals, but you'll have to invent your own tooling for
> checkouts, updates, commits, etc.
Yea, I
On 26.04.2016 20:32, Grant Edwards wrote:
> On 2016-04-26, Branko Čibej wrote:
>> On 26.04.2016 02:09, Grant Edwards wrote:
>>> Thanks again! Now I just have to decided whether to use
>>> intra-repository externals or nested working copies to share
>>> directories of source code among a group of p
On 2016-04-26, Branko Čibej wrote:
> On 26.04.2016 02:09, Grant Edwards wrote:
>> Thanks again! Now I just have to decided whether to use
>> intra-repository externals or nested working copies to share
>> directories of source code among a group of projects. It may depend on
>> how smartsvn handle
On 26.04.2016 02:09, Grant Edwards wrote:
> Thanks again! Now I just have to decided whether to use
> intra-repository externals or nested working copies to share
> directories of source code among a group of projects. It may depend on
> how smartsvn handles tagging/branching that involves external
On 26.04.2016 01:27, Stefan wrote:
> Hi Edwards,
>> A couple questions regarding "svn copy --pin-externals":
>>
>> 1) I thought I saw that when the --pin-externals option was being
>> developed it handled things differently when the destination was a
>> tag verses a branch.
>>
>> IIRC,
On 2016-04-25, Stefan wrote:
> Hi Edwards,
>> A couple questions regarding "svn copy --pin-externals":
>>
>> 1) I thought I saw that when the --pin-externals option was being
>> developed it handled things differently when the destination was a
>> tag verses a branch.
>>
>> IIRC, copy
Hi Edwards,
A couple questions regarding "svn copy --pin-externals":
1) I thought I saw that when the --pin-externals option was being
developed it handled things differently when the destination was a
tag verses a branch.
IIRC, copy --pin-externals to a "tag" destination just pinne
A couple questions regarding "svn copy --pin-externals":
1) I thought I saw that when the --pin-externals option was being
developed it handled things differently when the destination was a
tag verses a branch.
IIRC, copy --pin-externals to a "tag" destination just pinned the
revision
