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

Re: RFC: Fixing "svn switch --relocate"

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-10-18 15:21:02 CEST

kfogel@collab.net writes:

> 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)

"If they differ" is unnecessary because all of this is under "If the
new URL does not match the old repository root" (which actually should
have been stated as, "If the repository root of the new URL does not
match the old repository root").

> Else if the uuids don't match:
> ERROR, as we do currently I believe

Well, duh. :-)

> 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.

Close, but not quite. It may be a no-op only if the path-in-repos is
not changing AND the working is not out of date with respect to that
path-in-repos. Yes, part of the grand unification is to make sure
that 'svn switch' always behaves like 'svn switch'.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 18 15:56:45 2004

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.