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

Re: Possible WC format bump

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Wed, 14 Mar 2012 18:28:40 +0000

"C. Michael Pilato" <cmpilato_at_collab.net> writes:

> On 03/14/2012 01:58 PM, Philip Martin wrote:
>> $ svn mv wc/A/g wc/g # using trunk
>> A wc/g
>> D wc/A/f
>> $ svn st wc # using trunk
>> D wc/A/f
>> > moved to wc/g
>> A + wc/g
>> > moved from wc/A/f
>>
>> If we now use the branch on that working copy:
>>
>> $ svn st wc
>> D wc/A/f
>> A + wc/g
>>
>> The moved-to/from is lost, a bit like 1.7 which simply doesn't consider
>> moved-to/from
>
> What happens in the opposite case -- that is, when you have a
> branch-based working copy and you move something, then use a stable
> 1.7 client to access it?

The stable 1.7 client will ignore the moved-to/here completely and treat
the move as copy+delete.

Current trunk will ignore most of moved-to/here create by the branch and
will usually treat the move as copy+delete, but it's not ignoring it
like 1.7 so I suppose some operations may fail. Similarly while the
branch will ignore most moved-to/here created by current trunk I can't
be certain it will ignore it in all cases.

-- 
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com
Received on 2012-03-14 19:29:17 CET

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