Hello Bert,
thanks for your reply. From my understanding svn does support svn:externals
references within the same repository and also that identical sub-trees
will exist multiple times in the working copy structure (i,e, the main wc
and the external wc's).
I modified the script to make the sub-t
On 08.04.2015 20:00, Evan Driscoll wrote:
> [I typoed some keys and apparently happened to hit send while still
> typing; let's try again. Sorry for the spam.]
>
> On Fri, Apr 3, 2015 at 4:25 PM, Branko Čibej wrote:
>> Would this tell you what you need (given a checkout of 'trunk'):
>>
>> svn
[I typoed some keys and apparently happened to hit send while still
typing; let's try again. Sorry for the spam.]
On Fri, Apr 3, 2015 at 4:25 PM, Branko Čibej wrote:
> Would this tell you what you need (given a checkout of 'trunk'):
>
> svn diff --summarize ^/trunk@ .
>
> This will give you a
On Fri, Apr 3, 2015 at 4:25 PM, Branko Čibej wrote:
> Would this tell you what you need (given a checkout of 'trunk'):
>
> svn diff --summarize ^/trunk@ .
>
> This will give you a summary of the differences between your current
> working copy state and the tree in the repository at .
Sorry fo
You are adding a directory ‘ext’, which makes it a versioned path *inside* the
repository/working copy and then in the parent directory you set a property
that it is something *external*.
A path can’t be versioned as part of the working copy and be an external at the
same time.
Once a p
Dear all,
using svn 1.8.11 changing an existing svn:externals property to a
sub-directory thereof will result in an "... is not a working copy root"
(combination of W20, W155007 and E205011). The attached sequence of
commands [1] will reproduce the behavior from scratch (Windows batch
syntax).
