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

Re: relocate doesn't check arguments - may screw up working copy

From: SteveKing <steveking_at_gmx.ch>
Date: 2004-05-13 18:40:09 CEST

Max Bowsher wrote:

> Read Ben's reply carefully.
> To clarify:
> If the WC is checkout out from:
> http://some.server/path/to/repository/trunk/foo
> then all of the following are valid X-es:
> http://some.server/path/to/repository/
> http://some.server/path/to/repository
> http://some.server/path/to/reposi
> http://some.server/path/to
> http://some.server/path/
> http://some.server/
> http://some
> http://
> http:

I did read it carefully :)
This is usefull if you don't want to specify the complete URL for the
relocate. So if the server changes from http://server1.com/repos/ to
http://server2.com/repos/ you could do
svn switch --relocate http://server1 http://server2
to relocate your working copy. But as I already mentioned, if you do a
svn switch --relocate . http://server2.com/repos/
you will end up with a working copy which points to a crippled URL.

So my suggestion is that the relocate only takes one argument (the "to"
URL). But you would have to specify the full URL to the new repository
for that to work:
svn switch --relocate http://server2.com/repos
would then read the "from" URL from the working copy where the command
was executed and substitute that with the "to" URL.


Love is photosensitive. It needs darkness to develop.
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 13 18:41:57 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.