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

SteveKing wrote:
> Ben Collins-Sussman wrote:
>
>> On Thu, 2004-05-13 at 10:59, SteveKing wrote:
>>
>>
>>> I was wondering why the --relocate command needs two URL's. The command
>>> needs to be executed inside a working copy so it knows where to start -
>>> so why does it need a "from" URL? It could read that URL from the
>>> working copy - or am I completely wrong here?
>>
>>
>> Because --relocate is just running a mindless textual substitution,
>> something like s/X/Y/ on each URL. You need to specify X and Y.
>>
>> X might be "http://" and Y might be "svn://". Or X might be
>> "http://oldhostname" and Y might be "http://newhostname". Or X might be
>> "http://host/oldreposlocation" and Y might be
>> "http://host/newreposlocation".
>
> I figured that from the URL's I got when I used the command wrong. But
> isn't the X URL always the URL the working copy is checked out from? So
> X could be read out from the working copy. Or is there another use for
> the relocate command?

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:

Max.

---------------------------------------------------------------------
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:33:10 2004