[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: Philip Martin <philip.martin_at_wandisco.com>
Date: Fri, 18 Jan 2013 10:20:02 +0000

"Bert Huijben" <bert_at_qqmail.nl> writes:

> 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

I think:

 svn mv A B
 svn mv B A

is shorthand for:

 svn mv A X
 svn mv B A
 svn mv X B

If so then a subsequent:

 svn mv A C

should result in A->B and B->C but it appears there is a bug in the
implementation. The result is B->C but the A->B move gets lost.

Certified & Supported Apache Subversion Downloads:
Received on 2013-01-18 11:20:43 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.