Re: svn commit: r1434913 - /subversion/trunk/subversion/libsvn_wc/wc_db.c
From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Fri, 18 Jan 2013 16:25:04 +0000 (GMT)
Stefan Sperling wrote:
> On Fri, Jan 18, 2013 at 04:52:42PM +0100, Stefan Sperling wrote:
+1. This is the only sensible behaviour for the user. The issue #3429  ("svn mv A B; svn mv B A" generates replace without history) was 'fixed' for 1.7 in a way that made the node 'Replaced', and even there I hope we can agree that was a pretty marginally acceptable solution for 1.7. We could have done it 'properly' there, but didn't. Now that we have local moves, it would be so, so wrong to keep doing that 'Replaced' thing.
I added a sentence to this effect in the 'Subcommand' table in <https://wiki.apache.org/subversion/LocalMoves>: "If moved back to its own 'from' path, it should become as if it had never been moved.".
This is an archived mail posted to the Subversion Dev mailing list.