On Fri, Jan 18, 2013 at 10:43 AM, Stefan Sperling <s...@elego.de> wrote:
> On Thu, Jan 17, 2013 at 10:14:11PM +0100, Bert Huijben wrote:
>> I think
>> $ svn mv A B
>> $ svn mv B A
>>
>> Will now store moved_from and moved_to in the same record, at the op-depth
>> of A.
>> (Or copy_tests.py move_file_back_and_forth wouldn't show moved_from and
>> moved_to on a single node using status using the code snippet here)
>>
>> How will this store a future move
>> $ svn mv A C
>
> You're not giving a complete command sequence here.
> I'm not sure I really understand what you mean.
> I'll try to fill in the blanks with something that makes sense.
I think Bert meant (with A being a versioned node already):
$ svn mv A B
$ svn mv B A
$ svn mv A C
But that seems to be working fine, AFAICS (at least it seems so in the UI):
[[[
C:\research\svn\experiment\testmove\wc>svn add A
A A
C:\research\svn\experiment\testmove\wc>svn commit -mm
Adding A
Transmitting file data .
Committed revision 1.
C:\research\svn\experiment\testmove\wc>svn up
Updating '.':
At revision 1.
C:\research\svn\experiment\testmove\wc>svn st
C:\research\svn\experiment\testmove\wc>svn mv A B
A B
D A
C:\research\svn\experiment\testmove\wc>svn st
D A
> moved to B
A + B
> moved from A
C:\research\svn\experiment\testmove\wc>svn mv B A
A A
D B
C:\research\svn\experiment\testmove\wc>svn st
R + A
> moved to A
> moved from A
C:\research\svn\experiment\testmove\wc>svn mv A C
A C
D A
C:\research\svn\experiment\testmove\wc>svn st
D A
> moved to C
A + C
> moved from A
]]]
--
Johan
