[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 10:43:35 +0100

On Thu, Jan 17, 2013 at 10:14:11PM +0100, Bert Huijben wrote:
> 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

You're not giving a complete command sequence here.
I'm not sure I really understand what you mean.
I'll try to fill in the blanks with something that makes sense.

The sequence:

svn mv A B
svn mkdir A
svn mv A C

In my opinion this should be equivalent to:

svn mv A B
svn mkdir C

Why do you want to store a move for A -> C?

If you move a node that isn't present in op_depth == 0, you don't need
to preserve the old location of the node. The node is now added at a
different path C, whereas before the move is was added at A.
Received on 2013-01-18 10:44:12 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.