[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r1434913 - /subversion/trunk/subversion/libsvn_wc/wc_db.c

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 18 Jan 2013 17:01:02 +0100

On Fri, Jan 18, 2013 at 04:52:42PM +0100, Stefan Sperling wrote:
> like 'svn mv A B; svn mv B A' earlier, which
> also doesn't make sense).

What I mean here is that I think this command sequence should
result in a no-op as far as the move operation is concerned.

Rather than running a copy+delete of B->A again as the current implementation
does, I think svn should undo the A->B move in a way that preserves any
existing modifications within B, so that the squence:

svn mv A B
svn mv B A

is a no-op, and the sequence:

svn mv A B
# make changes in B
svn mv B A

results in the equivalent of:

# make changes in A

I'm considering trying to work on this soon.
Received on 2013-01-18 17:01:40 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.