Karl Fogel wrote:
> Philip Martin <philip@codematters.co.uk> writes:
>>> If only the server name has changed, then 'svn switch' will get
>>> your URLs changed without trouble. That is because it will see
>>> that your original repository and the "new" one (via the new URL)
>>> are exactly the same.
>>
>> One usage mentioned earlier is the case when the original URL is no
>> longer accessible.
>
> Yes, that's it, thanks for remembering Philip.
>
> I think the point is that this should be purely a textual change.
> It shouldn't involve network operations. So (I think) a new command
> actually is appropriate here...
New command or flag to the 'switch', doesn't matter to me. I've
personally run into this very same problem as well - when the hostname
changed for my repository.
Oh BTW, I'm probably missing something major, but - why can't we
switch to a new repository without first contacting the old one? I
mean - we have the old text bases, we have our local edits - and then
we are getting the new text baseses - can't we just "normally" merge
the local edits into the new text-bases and be happy with it? Or maybe
there is a case where switching is not equivalent to checking out a
new working copy and doing 'svn diff | patch' from the old to the new?
But in any case, the original point is sane - I do have wanted to just
change the URL, without being able to contact the old server, since it
is that very server that decided to change names.
-- Naked
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 18 09:41:16 2002