Re: Move tracking and NODES.moved_to/moved_here

Philip Martin <philip.martin_at_wandisco.com> writes:

> State 3: after A/B to A/B2 then A to A2
> op_depth local_relpath presence moved_here moved_to
> 0 A normal A2
> 0 A/B normal A2/B

Typo, moved_to should be A2/B2.

> 1 A base-deleted
> 1 A/B base-deleted
> 1 A2 normal 1
> 1 A2/B normal
> 2 A2/B base-deleted
> 2 A2/B2 normal 1
>
> Which of these is correct, A2/B moved_here or not?

In r1213651 I've made A2/B get marked moved_here. So now the states are:

State 1: after A to A2
op_depth local_relpath presence moved_here moved_to
      0 A normal A2
      0 A/B normal
      1 A base-deleted
      1 A/B base-deleted
      1 A2 normal 1
      1 A2/B normal 1

State 1x: after A/B to A/B2
op_depth local_relpath presence moved_here moved_to
      0 A normal
      0 A/B normal A/B2
      2 A/B base-deleted
      2 A/B2 normal 1

State 2: after A to A2 then A2/B to A2/B2
State 3: after A/B to A/B2 then A to A2
op_depth local_relpath presence moved_here moved_to
      0 A normal A2
      0 A/B normal A2/B2
      1 A base-deleted
      1 A/B base-deleted
      1 A2 normal 1
      1 A2/B normal 1
      2 A2/B base-deleted
      2 A2/B2 normal 1

-- 
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com