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

Re: Question: Best way to branch after changes have already been made

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2005-04-26 19:26:05 CEST

On Tue, 2005-04-26 at 12:10, Mike Harris wrote:
> 2. I don't think this even works, but I could relocate (switch
> --relocate) my WC from trunk to the new branch and check in. This would
> be great, but I don't believe relocate can be used in this fashion.

"svn switch --relocate" is *only* for the case where the way you access
your repository has changed. It is not for moving around within a
repository; trying to use it for that purpose will break your working
copy. Some day we hope to have a unified switch operation which handles
both cases and is safe, but right now you have to be very careful to
only use "svn switch --relocate" for its intended purpose and to give it
correct arguments.

I think a regular "svn switch" to the new branch would work fine, but
Josh Siegel's answer (using "svn cp" to copy your working copy to a new
branch) is superior.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 26 19:31:35 2005

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