[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: Martin Furter <mf_at_rola.ch>
Date: 2005-08-24 01:36:29 CEST

On 23 Aug 2005, C. Michael Pilato wrote:

> "Peter N. Lundblad" <peter@famlundblad.se> writes:
> > So, I thin k the check should be changed so that it only checks that the
> > prefix of the arguments that change are part of the repository root, but
> > accept a path thereafter if it is identical in both strings. As I
> > discussed with Karl on IRC, this shouldn't just silently error, but
> > instead violently generate an error instead. Agreed?
> Let me see if I have this straight. Ensure that:
> - URL-of-WC-target is or is a child of FROM-URL,
> - upon removal of the relative path from FROM-URL to
> URL-of-WC-target from TO-URL, we wind up the new repository root.
> Is that right?

Will it be posible to circumvent that check (using --force) ?

A scenario I had was that I had to move the location of some home
directories in the repos.

I thought if I "svn mv" them and do an "avn up $HOME" I get a huge mess,
things get removed, some directories stay there with unversioned content,

So i chose to do some repos surgery: dump the repos, move the home dirs by
processing the dump (using the merge command of my svndumptool.py) and
load that dump. After that relocate did the right thing. That wouldn't be
possible if I can't circumvent that check.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 24 01:38:21 2005

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.