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

Re: svn switch to an incorrect branch deletes modified local files

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Fri, 25 Apr 2008 07:58:23 -0400

Mark Phippard wrote:
> On Wed, Apr 23, 2008 at 8:47 PM, Eric Gillespie <epg_at_pretzelnet.org> wrote:
>> Eric Gillespie <epg_at_pretzelnet.org> writes:
>> > svn sw ^/branches => OOPS
>> >
>> > That sucks even on a sane-sized project. On a big ball of mud?
>> > CRIPES! So what do poor lusers do after it chugs along for way
>> > too long? They interrupt it. Hello wc corruption.
>> Glasser just had a good idea: allow the esoteric switch only if
>> the user gives the --ignore-ancestry; otherwise, error out on any
>> switch to a path that doesn't share ancestry.
> Mike Pilato (and Glasser) would know better, but didn't we create some
> new API for merge that would make checking this ancestry really easy
> now? I think it would be a good idea too.

I was already thinking of using svn_client__get_youngest_common_ancestor()
to make this check. And --ignore-ancestry as a more-appropriately-name
"force" flag sounds great. +1 all over this.

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2008-04-25 13:58:36 CEST

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.