Re: Understanding move merge

Philip Martin wrote:

Philip Martin philip@codematters.co.uk writes:
  

So in the move+modify case, where a new node needs to be created, I
suppose it would look like

        / (0.0.5)
           A/ (a.0.5)
              bar (r.0.3)
           B/ (b.0.5)
              baz (f.1.5)
    

Perhaps baz (f.0.5)?

Exactly! The move does not create a new branch.

              qux (q.0.4)

Will this be a problem? Does it mean that the client will be unable
to distinguish copy+delete from move+modify?
    

Then it would be distinct from copy :) Yes, that does look more like
what we want.
  

Hey, a convert! Welcome to the world of twisty little branches, all
alike. :-)

-- 
Brane Čibej   brane_at_xbc.nu   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org