cvs-usage revision 499b34cea04a46823d003d4c0520c8b03e8513cb
e74100e3f43887f048643973a1f4351daa3a9628Brian WellingtonCopyright (C) 2000, 2001 Internet Software Consortium.
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark AndrewsSee COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark AndrewsNotes on CVS Usage
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark Andrews
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark AndrewsAccessing the repository
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
70e5a7403f0e0a3bd292b8287c5fed5772c15270Automatic UpdaterThe recommended way of accessing the BIND 9 CVS repository is by ssh
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austeinto rc.isc.org, using the following environment settings:
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington CVSROOT=:ext:rc.isc.org:/proj/cvs/isc
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington CVS_RSH=ssh
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
e74100e3f43887f048643973a1f4351daa3a9628Brian WellingtonCreating a release branch
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
e74100e3f43887f048643973a1f4351daa3a9628Brian WellingtonHere's how the 9.0 release branch was created:
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington cvs rtag v9_0_base bind9
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington cvs rtag -b -r v9_0_base v9_0 bind9
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
e74100e3f43887f048643973a1f4351daa3a9628Brian WellingtonRenaming files by respository copy
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark Andrews
e74100e3f43887f048643973a1f4351daa3a9628Brian WellingtonWhen you need to rename or move a file that is under CVS control, use
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellingtonthe "repository copy" method as described in the following text
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellingtonborrowed from an ancient CVS FAQ:
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington 2C.4 How do I rename a file?
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington CVS does not offer a way to rename a file in a way that CVS can
e74100e3f43887f048643973a1f4351daa3a9628Brian Wellington track later. See Section 4B for more information.
Here is the best way to get the effect of renaming, while
preserving the change log:
1. Copy the RCS (",v") file directly in the Repository.
cp $CVSROOT/<odir>/<ofile>,v $CVSROOT/<ndir>/<nfile>,v
2. Remove the old file using CVS.
By duplicating the file, you will preserve the change
history and the ability to retrieve earlier revisions of the
old file via the "-r <tag/rev>" or "-D <date>" options to
"checkout" and "update".
cd <working-dir>/<odir>
rm <ofile>
cvs remove <ofile>
cvs commit <ofile>
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
the renaming.
cd <working-dir>/<ndir>
cvs update <nfile>
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 v9_0_base file
cvs tag -b -r v9_0_base v9_0 file
$Id: cvs-usage,v 1.6 2001/01/09 21:47:00 bwelling Exp $