On 12/7/07, Jaime Villate <villate at fe.up.pt> wrote:
> 1- After the creation of the release branch is announced, I make a fresh
> new copy of the CVS repository, with the release branch:
> cvs -d :ext:villate at maxima.cvs.sourceforge.net:/cvsroot/maxima co -r
> "RELEASE-5_14_0-BRANCH" maxima
>
> 2- I continue making changes and committing them in the old repository
> (with the CVS head branch). If a change should also be in the release
> branch and I think it is safe to put it there, I will copy the file to
> the copy of the release branch and commit it there too.
Hmm, this seems more complicated than it needs to be.
cvs update -r whatever-tag-or-branch -dP
changes the sandbox files to the tagged version.
cvs update -dAP
makes cvs forget the tag and go back to the trunk.
Those commands can be applied to a single directory or file.
So it's really not necessary to maintain two separate sandboxes;
it should be enough to use cvs update to switch between the
branch and the trunk. But if someone is more happier with
two sandboxes, then I certainly won't stop them.
FWIW
Robert Dodier