You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "C. Michael Pilato" <cm...@collab.net> on 2010/11/03 18:27:29 UTC
Re: Upgrading partially relocated working copies
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*!"
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: Upgrading partially relocated working copies
Posted by "C. Michael Pilato" <cm...@collab.net>.
On 11/04/2010 07:23 AM, Philip Martin wrote:
> 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.
RESOLVED/WORKSFORME
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: Upgrading partially relocated working copies
Posted by Philip Martin <ph...@wandisco.com>.
"C. Michael Pilato" <cm...@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.
--
Philip