Daniel Shahaf wrote:
>Anton Shepelev wrote on Wed, 29 Nov 2017 20:18 +0300:
>> Why can 'svn ls' show different results when invoked from
>> two working copies of the same repository?
>
>Probably because the working copy's BASE revision is different. 'svn ls'
>runs 'svn ls .@BASE' by default. If y
On 29.11.2017 18:34, Daniel Shahaf wrote:
> Anton Shepelev wrote on Wed, 29 Nov 2017 20:18 +0300:
>> Why can 'svn ls' show different results when invoked from
>> two working copies of the same repository?
> Probably because the working copy's BASE revision is different. 'svn ls'
> runs 'svn ls .@B
Daniel Shahaf to Anton Shepelev:
> > Why can 'svn ls' show different results when invoked
> > from two working copies of the same repository?
>
> Probably because the working copy's BASE revision is
> different. 'svn ls' runs 'svn ls .@BASE' by default.
Disregarding what is writ in the Book?
>
Anton Shepelev wrote on Wed, 29 Nov 2017 20:18 +0300:
> Why can 'svn ls' show different results when invoked from
> two working copies of the same repository?
Probably because the working copy's BASE revision is different. 'svn ls'
runs 'svn ls .@BASE' by default. If you pass an explicit revisio
Hello, all
Why can 'svn ls' show different results when invoked from
two working copies of the same repository? According to the
documentation is should always list the acutal contents of
the corresponding repository:
The default TARGET is ., meaning the repository URL of the
current working
