Greg Hudson <ghudson@MIT.EDU> writes:
> PHASE 3: Profit!
>
> We modify "svn switch" (without the relocate flag) as follows:
>
> If the new URL does not match the old repository root:
> Contact the new URL and ask for the uuid and new repository root
> If the new uuid matches the old uuid:
> Relocate from the old repository root to the new one
> Finish by doing a regular "svn switch" to the new URL
>
> Then we deprecate "svn switch --relocate" and remove it in 2.0.
>
> Comments? I will file an enhancement issue for this plan if no one
> objects. I don't have immediate plans to implement it, so other
> people should feel free to jump on it.
I like the plan -- and we've needed to separate repos-root from
path-in-repos in working copies for a long time, for various reasons,
so this would bring benefits beyond relocate.
I'm a little unclear on step 3. Should it be this instead?:
If the new URL does not match the old repository root:
Contact the new URL and ask for the uuid and new repository root
If the new uuid matches the old uuid:
Relocate from old repository root to new one (if they differ)
Else if the uuids don't match:
ERROR, as we do currently I believe
Finish with a regular "svn switch" to the new URL (might be a no-op)
By "no-op", I mean, it might be that the only thing changing is the
repository root portion, and the path-in-repos is not changing.
Also, when I say "repository root" above, it really means
hostname+reposroot. I assume you informally meant that in your
algorithm too?
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 18 08:32:16 2004