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

Re: Adopting our best practices to svn?

From: Scott Gifford <sgifford_at_suspectclass.com>
Date: 2007-07-26 03:22:53 CEST

Mike Meyer <mwm-keyword-svn.257b71@mired.org> writes:


> When we have a change that's going to result in an unstable tree for
> any period of time, we create a branch to work on. We then follow
> that sage advice, and "merge early and often", adding changes in the
> trunk to our branch on a regular basis. When the change is done, we
> merge in any remaining changes from trunk, run our regression tests,
> and then we're through. At this point, we want the trunk to become a
> copy of the branch.
> And that copy is the sticking point. "svn copy" won't work, because
> the trunk is already populated.


Would something like:

    svn mv trunk oldtrunk
    svn mv branch trunk

do what you want? Obviously using more useful names.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 26 03:22:09 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.