[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: Josh Siegel <joshs_at_stormbirds.org>
Date: 2005-04-26 19:19:40 CEST

You can copy directly from your working area to a branch and it will "do
the right thing" including grabbing all your local mods

go to the root and do a

"svn copy . http://foo/branches/shelf"

    -josh

Mike Harris wrote:

> Here's my situation. I have made changes to my working copy of our
> trunk. After making a week's worth of changes, I now need to shelve
> the changes and move on to something else. What I want to do is check
> these changes into a branch, but my working copy points to the trunk.
> What is the best way to accomplish this? There are a couple ways I
> know of to do it, but they seem sub-optimal.
>
> 1. I could create the branch of trunk, check out a working copy, then
> copy the modified files into the branch working copy and check it in
>
> 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.
>
> Any suggestions would be appreciated. Thank you.
>
> Mike Harris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>

---------------------------------------------------------------------
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:20:40 2005

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