Re: Understanding move merge

William Uther willu@cse.unsw.edu.au writes:

 The proposed move semantics need to define what happens during a
 merge when one end of a merge contains only one end of a move. I was
 thinking that it might just devolve to copy+delete semantics in this
 case (or possibly error, but devolve with a -force tag?):
[...]
 I don't think you can get away with the same approach as commits where
 you simply disallow such merges. You at least need to allow them with
 '-force'.

I certainly would not want atomic move to degenerate into delete/copy
by default, although I suppose it would be OK to have a flag to enable
that. Note that this sort of problem is not really new, there is a
similar problem when the merge source modifies a file that does not
exist in the merge target. At present attempting such a merge just
produces a not under revision control error, although perhaps we
ought to do better :)

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org