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

Re: Possible issue triggered by repos reorg (including repro script)

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-04-17 03:35:21 CEST

On Apr 16, 2005, at 6:51 PM, Matt Doran wrote:

>   1. Update the working copy to mirror a new URL within the
> repository.
>      This behaviour is similar to 'svn update', and is the way to
>      move a working copy to a branch or tag within the same
> repository.
>   2. Rewrite working copy URL metadata to reflect a syntactic change
> only.
>      This is used when repository's root URL changes (such as a schema
>      or hostname change) but your working copy still reflects the same
>      directory within the same repository.

The help text could be improved. I just added more explanation to
chapter 9 in the svn book as well.

> Are there any checks that could be added to --relocate to avoid my
> mistake.  I.e. don't allow the relocate if the "SVNROOT" does change? 

Not yet, since the working copy, when looking at URL, doesn't know
where SVNROOT ends and the "internal repository" path begins. We plan
to change that someday.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 17 03:37:13 2005

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