10140N/ACopyright (C) 2000, 2001, 2004, 2016 Internet Systems Consortium, Inc. ("ISC")
10140N/A
10140N/AThis Source Code Form is subject to the terms of the Mozilla Public
10140N/ALicense, v. 2.0. If a copy of the MPL was not distributed with this
10143N/Afile, You can obtain one at http://mozilla.org/MPL/2.0/.
10140N/A
10140N/ANotes on CVS Usage
10140N/A
10143N/AAccessing the repository
10140N/A
10140N/A
10140N/AThe recommended way of accessing the BIND 9 CVS repository is by ssh
10140N/Ato rc.isc.org, using the following environment settings:
13477N/A
13477N/A CVSROOT=:ext:rc.isc.org:/proj/cvs/isc
13477N/A CVS_RSH=ssh
13477N/A
13477N/A
14020N/ACreating a release branch
14020N/A
14020N/A
14020N/AHere's how the 9.0 release branch was created:
13477N/A
10140N/A cvs rtag v9_0_base bind9
10140N/A cvs rtag -b -r v9_0_base v9_0 bind9
10140N/A
10140N/A
10140N/A
10140N/ARenaming files by respository copy
10140N/A
10140N/A
10140N/AWhen you need to rename or move a file that is under CVS control, use
17777N/Athe "repository copy" method as described in the following text
15204N/Aborrowed from an ancient CVS FAQ:
10140N/A
10140N/A 2C.4 How do I rename a file?
15204N/A
15204N/A CVS does not offer a way to rename a file in a way that CVS can
10140N/A track later. See Section 4B for more information.
10140N/A
10140N/A Here is the best way to get the effect of renaming, while
10140N/A preserving the change log:
10140N/A
10140N/A 1. Copy the RCS (",v") file directly in the Repository.
10140N/A
10140N/A cp $CVSROOT/<odir>/<ofile>,v $CVSROOT/<ndir>/<nfile>,v
10140N/A
10140N/A 2. Remove the old file using CVS.
10140N/A
10140N/A By duplicating the file, you will preserve the change
10140N/A history and the ability to retrieve earlier revisions of the
10140N/A old file via the "-r <tag/rev>" or "-D <date>" options to
10140N/A "checkout" and "update".
10140N/A
10394N/A cd <working-dir>/<odir>
10140N/A rm <ofile>
10140N/A cvs remove <ofile>
15204N/A cvs commit <ofile>
10140N/A
10140N/A 3. Retrieve <newfile> and remove all the Tags from it.
18713N/A
18713N/A By stripping off all the old Tags, the "checkout -r" and
18713N/A "update -r" commands won't retrieve revisions Tagged before
18713N/A the renaming.
18713N/A
18713N/A cd <working-dir>/<ndir>
18713N/A cvs update <nfile>
10140N/A cvs log <nfile> # Save the list of Tags
10140N/A cvs tag -d <tag1> <nfile>
10140N/A cvs tag -d <tag2> <nfile>
10140N/A . . .
10140N/A
10140N/A
10140N/A This technique can be used to rename files within one directory or
10140N/A across different directories. You can apply this idea to
10140N/A directories too, as long as you apply the above to each file and
10140N/A don't delete the old directory.
10140N/A
10140N/A Of course, you have to change the build system (e.g. Makefile) in
10140N/A your <working-dir> to know about the name change.
10140N/A
10140N/A
10140N/APulling up a newly added file to a release branch:
10140N/A
10140N/AIn a mainline working tree, do something like this:
10140N/A
10140N/A cvs tag v9_0_base file
10140N/A cvs tag -b -r v9_0_base v9_0 file
10140N/A
10140N/A
10140N/AImporting contrib source from vendor release
10140N/A
10140N/AAs an example, here's how queryperf was imported:
10140N/A
10140N/A cd /tmp
10140N/A cvs -d shell.nominum.com:/proj/cvs/nominum export -rHEAD queryperf
10140N/A cd queryperf
10140N/A cvs -d rc.isc.org:/proj/cvs/isc import bind9/contrib/queryperf \
10140N/A NOMINUM NOMINUM_20010710
10140N/A
10140N/A
10140N/A
10140N/A$Id: cvs-usage,v 1.8 2004/03/05 05:04:50 marka Exp $
10140N/A