1N/ACopyright (C) 2000 Internet Software Consortium.
1N/AAccessing the repository
1N/AThe recommended way of accessing the BIND 9 CVS repository is by ssh
1N/ARenaming files by respository copy
1N/AWhen you need to rename or move a file that is under CVS control, use
1N/Athe "repository copy" method as described in the following text
1N/Aborrowed from an ancient CVS FAQ:
1N/A 2C.4 How do I rename a file?
1N/A CVS does not offer a way to rename a file in a way that CVS can
1N/A track later. See Section 4B for more information.
1N/A Here is the best way to get the effect of renaming, while
1N/A preserving the change log:
1N/A 1. Copy the RCS (",v") file directly in the Repository.
1N/A cp $CVSROOT/<odir>/<ofile>,v $CVSROOT/<ndir>/<nfile>,v
1N/A 2. Remove the old file using CVS.
1N/A By duplicating the file, you will preserve the change
1N/A history and the ability to retrieve earlier revisions of the
1N/A old file via the "-r <
tag/rev>" or "-D <date>" options to
1N/A "checkout" and "update".
1N/A cd <working-dir>/<odir>
1N/A 3. Retrieve <newfile> and remove all the Tags from it.
1N/A By stripping off all the old Tags, the "checkout -r" and
1N/A "update -r" commands won't retrieve revisions Tagged before
1N/A cd <working-dir>/<ndir>
1N/A cvs log <nfile> # Save the list of Tags
1N/A cvs tag -d <tag1> <nfile>
1N/A cvs tag -d <tag2> <nfile>
1N/A This technique can be used to rename files within one directory or
1N/A across different directories. You can apply this idea to
1N/A directories too, as long as you apply the above to each file and
1N/A 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-usage,v 1.2 2000/06/21 23:48:13 tale Exp $