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

Re: Relocate Problem

From: Scott Palmer <scott.palmer_at_2connected.org>
Date: 2005-05-25 17:13:36 CEST

On May 25, 2005, at 10:16 AM, Ben Collins-Sussman wrote:

> On May 25, 2005, at 8:35 AM, Scott Palmer wrote:
>
>> I needed the switch because the location of the project within the
>> repo changed
>
> Ok, then what you wanted was a relocation, not a switch. In other
> words, all you wanted was for some process to dumbly rewrite the
> URLs stored in your .svn/ area, so that things would appear as if
> the project had always been at the new repository location.
>
> So a simple 'svn switch --relocate' would have worked for you.

Except that you've written before that using --relocate to "switch"
when it wasn't just the protocol or path to the repository that
changed is BAD. If the path within the repository changes we have
been told to NOT use --relocate because it will hose stuff.

Wouldn't what I mentioned about not finding the BASE revision at the
new path cause a problem if I had only used --relocate?

Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 25 17:15:13 2005

This is an archived mail posted to the Subversion Users mailing list.