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

Re: 'svn switch --relocate' behavior change -- intentional?

From: Branko ─îibej <brane_at_xbc.nu>
Date: 2005-08-23 22:33:51 CEST

C. Michael Pilato wrote:

>Yesterday I noticed the suddenly 'svn switch --relocate' didn't work
>the same way it always has, requiring now that instead of using a
>FROM_URL and TO_URL which reflected the locations of the relocation's
>working copy target path, the FROM_URL and TO_URL must be repository
>root URLs.
>For example, I used to do:
> svn switch --relocate .../repos/trunk .../repos/trunk trunk-wc
>But now that errors out, and I'm forced to do:
> svn switch --relocate .../repos .../repos trunk-wc
>Was this change in behavior intentional? The log message for r15015
>seems to indicate that something was intended:
> ...
> * subversion/libsvn_wc/relocate.c (relocate_entry): Don't rewrite any URLs
> if the FROM argument matches outside the repository root URL. Rewrite the
> repos root URL.
> ...
>Did the community accept this change in behavior, and I just missed it?
I think it surprised me at one time, too. Besides, I don't believe this
behaviour is what the commit was supposed to fix.

IIRC, we wanted to disallow the relocate if it changed, say foo://bar to
foo://baz, where the new repos root was in fact foo://baz/blah (that is,
if the relocate parameters were shorter than the repository root). I
don't think that longer relocate params should be disallowed.

-- Brane

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 23 22:35:04 2005

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