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. The sequence: svn mv A B svn mkdir A svn mv A C In my opinion this should be equivalent to: svn mv A B svn mkdir C Why do you want to store a move for A -> C? If you move a node that isn't present in op_depth == 0, you don't need to preserve the old location of the node. The node is now added at a different path C, whereas before the move is was added at A.
