On Tue, Oct 18, 2011 at 01:03:23AM +0200, Stefan Sperling wrote: > On Mon, Oct 17, 2011 at 03:44:11PM +0200, Bert Huijben wrote: > > What if the child was moved to a different location than its parent? > > > > $ svn mv A/child B/child > > $ svn mv A new_A > > > > $ svn up . > > Receives update for A/child > > Yes, that's a problem -- what happens is that the child goes missing. > Thanks for pointing it out.
See http://subversion.tigris.org/issues/show_bug.cgi?id=4037 I don't think we can solve this without the client knowing about the destination of the incoming move. The issue is marked as a 1.8 blocker to make sure the final release does something sane here.
