2N/ACopyright (C) 2000 Internet Software Consortium.
2N/AAccessing the repository
2N/AThe recommended way of accessing the BIND 9 CVS repository is by ssh
2N/ACreating a release branch
2N/AHere's how the 9.0 release branch was created:
2N/A cvs rtag v9_0_base bind9
2N/A cvs rtag -b -r v9_0_base v9_0 bind9
2N/ARenaming files by respository copy
2N/AWhen you need to rename or move a file that is under CVS control, use
2N/Athe "repository copy" method as described in the following text
2N/Aborrowed from an ancient CVS FAQ:
2N/A 2C.4 How do I rename a file?
2N/A CVS does not offer a way to rename a file in a way that CVS can
2N/A track later. See Section 4B for more information.
2N/A Here is the best way to get the effect of renaming, while
2N/A preserving the change log:
2N/A 1. Copy the RCS (",v") file directly in the Repository.
2N/A cp $CVSROOT/<odir>/<ofile>,v $CVSROOT/<ndir>/<nfile>,v
2N/A 2. Remove the old file using CVS.
2N/A By duplicating the file, you will preserve the change
2N/A history and the ability to retrieve earlier revisions of the
2N/A old file via the "-r <
tag/rev>" or "-D <date>" options to
2N/A "checkout" and "update".
2N/A cd <working-dir>/<odir>
2N/A 3. Retrieve <newfile> and remove all the Tags from it.
By stripping off all the old Tags, the "checkout -r" and
"update -r" commands won't retrieve revisions Tagged before
cvs log <nfile> # Save the list of Tags
cvs tag -d <tag1> <nfile>
cvs tag -d <tag2> <nfile>
This technique can be used to rename files within one directory or
across different directories. You can apply this idea to
directories too, as long as you apply the above to each file and
don't delete the old directory.
Of course, you have to change the build system (
e.g. Makefile) in
your <working-dir> to know about the name change.
Pulling up a newly added file to a release branch:
In a mainline working tree, do something like this:
cvs tag -b -r v9_0_base v9_0 file
$Id: cvs-usage,v 1.3 2000/07/10 16:16:06 gson Exp $