[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: Branko Čibej <brane_at_wandisco.com>
Date: Fri, 18 Jan 2013 11:29:49 +0100

On 18.01.2013 11:20, Johan Corveleyn wrote:
> On Thu, Jan 17, 2013 at 10:59 PM, Ben Reser <ben_at_reser.org> wrote:
>> On Thu, Jan 17, 2013 at 1:14 PM, Bert Huijben <bert_at_qqmail.nl> 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)
>> This seems really ugly to me:
>> $ svn status
>> R + A
>> > moved to A
>> > moved from A
> Yeah, pretty ugly ... but perhaps it's not much uglier than the
> solution in 1.7 (without move tracking):
>
> $ svn status
> R + A
>
> Ideally svn should see that this "self-replacement with history" is
> perhaps better represented as a simple Modification.

In fact it's not even a modification, the second move just undoes the
first one and "svn status" should show nothing at all in this case.

-- Brane

-- 
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Received on 2013-01-18 11:30:35 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.