aa37793651f52858384f57a8d744b734d9a30950Ryan Grove

3937692b48191b3be82199e7379ee5161e442f32Adam Moore

3937692b48191b3be82199e7379ee5161e442f32Adam Moore

aa37793651f52858384f57a8d744b734d9a30950Ryan GroveNotes on CVS Usage

aa37793651f52858384f57a8d744b734d9a30950Ryan Grove

3937692b48191b3be82199e7379ee5161e442f32Adam Moore

cb4f4f79feb7498d1f3406b88fb62209e5f5a444Adam Moore

3937692b48191b3be82199e7379ee5161e442f32Adam MooreAccessing the repository

aa37793651f52858384f57a8d744b734d9a30950Ryan Grove

aa37793651f52858384f57a8d744b734d9a30950Ryan Grove

3937692b48191b3be82199e7379ee5161e442f32Adam MooreThe recommended way of accessing the BIND 9 CVS repository is by ssh

aa37793651f52858384f57a8d744b734d9a30950Ryan Groveto rc.isc.org, using the following environment settings:

aa37793651f52858384f57a8d744b734d9a30950Ryan Grove

aa37793651f52858384f57a8d744b734d9a30950Ryan Grove CVSROOT=:ext:rc.isc.org:/proj/cvs/isc

aa37793651f52858384f57a8d744b734d9a30950Ryan Grove CVS_RSH=ssh

aa37793651f52858384f57a8d744b734d9a30950Ryan Grove

aa37793651f52858384f57a8d744b734d9a30950Ryan Grove

aa37793651f52858384f57a8d744b734d9a30950Ryan Grove

aa37793651f52858384f57a8d744b734d9a30950Ryan GroveRenaming files by respository copy

aa37793651f52858384f57a8d744b734d9a30950Ryan Grove

3937692b48191b3be82199e7379ee5161e442f32Adam Moore

7d9f4a49ef5e163b5f38d09a20f72208ab859e65Ryan GroveWhen you need to rename or move a file that is under CVS control, use

aa37793651f52858384f57a8d744b734d9a30950Ryan Grovethe "repository copy" method as described in the following text

7d9f4a49ef5e163b5f38d09a20f72208ab859e65Ryan Groveborrowed from an ancient CVS FAQ:

aa37793651f52858384f57a8d744b734d9a30950Ryan Grove

aa37793651f52858384f57a8d744b734d9a30950Ryan Grove 2C.4 How do I rename a file?

3937692b48191b3be82199e7379ee5161e442f32Adam Moore

aa37793651f52858384f57a8d744b734d9a30950Ryan Grove CVS does not offer a way to rename a file in a way that CVS can

3937692b48191b3be82199e7379ee5161e442f32Adam Moore track later. See Section 4B for more information.

3937692b48191b3be82199e7379ee5161e442f32Adam Moore

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.

$Id: cvs,v 1.1 2000/06/01 21:00:44 gson Exp $