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

RE: [Bug?] svn moving A to B and B to A becomes replace

From: Johan Corveleyn <johan.corveleyn_at_uz.kuleuven.ac.be>
Date: Thu, 18 Jun 2009 14:29:57 +0200

> On Wed, Jun 17, 2009 at 02:12:43AM +0200, Johan Corveleyn wrote:
> > We have experienced some strange, and IMHO undesired, behavior. I've
> > searched the SVN bug database and mailinglists, but haven't found
> > anything exactly the same. Is this a bug?
> >
> > Short description: Moving a file in a WC (svn mv) to another
> filename,
> > then moving it back to the original filename, generates a "replace"
> > (i.e. a delete and add of another file with the same name, thereby
> > breaking the history).
> I'd say it's just a consequence of the current design (or
> lack thereof) of the rename operation.
> Maybe this is just part of the good old issue #898?
> http://subversion.tigris.org/issues/show_bug.cgi?id=898
> Stefan

Hm, while this issue could certainly be addressed as part of issue #898, it doesn't have to. I.e., I don't fully agree that this is part of that issue.

I can perfectly imagine the following happening, after issue #898 would be resolved (let's imagine, in the post-#898-era, moves are shown as modifications on the parent dir(s) with an additional note about the move):

$ svn mv test.txt test.txt2
M . (moved test.txt to test.txt2)

$ svn status -N
M . (moved test.txt to test.txt2)

$ svn mv test.txt2 test.txt
M . (moved test.txt2 to test.txt)

$ svn status -N
R test.txt

For this last status, I would expect either:
- SVN understands that this is a no-op, and just doesn't show it anymore as a local modification.
- SVN shows both moves, and also applies them on the server when committing:
$ svn status -N
M . (moved test.txt to test.txt2)
M . (moved test.txt2 to test.txt)

Besides, I don't think you need #898 to be solved to solve this issue. OTOH, if issue #898 is more likely to get addressed (in 1.8 let's hope), and this would be solved as a part of it, I would also be happy :).

If this is not logged as a new issue, then maybe we should at least at a note about this to #898, so that this is not overlooked.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-18 14:30:53 CEST

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