"Bert Huijben" <b...@qqmail.nl> writes: > 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
I think: svn mv A B svn mv B A is shorthand for: svn mv A X svn mv B A svn mv X B If so then a subsequent: svn mv A C should result in A->B and B->C but it appears there is a bug in the implementation. The result is B->C but the A->B move gets lost. -- Certified & Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
