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

Re: Upgrading partially relocated working copies

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Thu, 04 Nov 2010 11:23:50 +0000

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

> On 10/19/2010 10:59 AM, Philip Martin wrote:
>> In 1.7 we insist that "switch --relocate" only acts on a whole working
>> copy. In 1.6 we allow parts of the working copy to be relocated.
>> What should 1.7 do when upgrading a partially switched working copy?
>> At present it ignores partial relocation and upgrades the whole
>> working copy based on the repository root used in the working copy
>> root. Should it detect the partial relocation and throw an error?
> Is it possible to do the upgrade while preserving the mixed-location-ness?
> We decided to prevent folks from creating new mixed-location-ness[1] in 1.7,
> but I can't recall now if that was because our schema and logic flow
> demanded WC-wide uniformity, or if we just wanted to tighten up some
> looseness that didn't seem to make practical sense.
> [1] "That's not a real word!" "It is now -- I've used it *twice*!"

I don't think it makes sense for upgrade to preserve the
mixed-location-ness as the user could not use 1.7 to convert such a
working copy to single-location. The only sensible options are either
to detect the mixed-location-ness and abort the upgrade, or to ignore it
and upgrade to single-location. We currently do the latter and if the
location is wrong the user can use the relocate command after the
upgrade to fix it.

Received on 2010-11-04 12:24:33 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.