mirror of
https://github.com/isc-projects/bind9.git
synced 2026-04-23 07:07:00 -04:00
created file with notes on CVS usage
This commit is contained in:
parent
174a4f7b80
commit
7b0fae507e
2 changed files with 148 additions and 0 deletions
74
doc/dev/cvs
Normal file
74
doc/dev/cvs
Normal file
|
|
@ -0,0 +1,74 @@
|
|||
|
||||
|
||||
|
||||
Notes on CVS Usage
|
||||
|
||||
|
||||
|
||||
Accessing the repository
|
||||
|
||||
|
||||
The recommended way of accessing the BIND 9 CVS repository is by ssh
|
||||
to rc.isc.org, using the following environment settings:
|
||||
|
||||
CVSROOT=:ext:rc.isc.org:/proj/cvs/isc
|
||||
CVS_RSH=ssh
|
||||
|
||||
|
||||
|
||||
Renaming files by respository copy
|
||||
|
||||
|
||||
When you need to rename or move a file that is under CVS control, use
|
||||
the "repository copy" method as described in the following text
|
||||
borrowed from an ancient CVS FAQ:
|
||||
|
||||
2C.4 How do I rename a file?
|
||||
|
||||
CVS does not offer a way to rename a file in a way that CVS can
|
||||
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.
|
||||
|
||||
|
||||
|
||||
$Id: cvs,v 1.1 2000/06/01 21:00:44 gson Exp $
|
||||
74
doc/dev/cvs-usage
Normal file
74
doc/dev/cvs-usage
Normal file
|
|
@ -0,0 +1,74 @@
|
|||
|
||||
|
||||
|
||||
Notes on CVS Usage
|
||||
|
||||
|
||||
|
||||
Accessing the repository
|
||||
|
||||
|
||||
The recommended way of accessing the BIND 9 CVS repository is by ssh
|
||||
to rc.isc.org, using the following environment settings:
|
||||
|
||||
CVSROOT=:ext:rc.isc.org:/proj/cvs/isc
|
||||
CVS_RSH=ssh
|
||||
|
||||
|
||||
|
||||
Renaming files by respository copy
|
||||
|
||||
|
||||
When you need to rename or move a file that is under CVS control, use
|
||||
the "repository copy" method as described in the following text
|
||||
borrowed from an ancient CVS FAQ:
|
||||
|
||||
2C.4 How do I rename a file?
|
||||
|
||||
CVS does not offer a way to rename a file in a way that CVS can
|
||||
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.
|
||||
|
||||
|
||||
|
||||
$Id: cvs-usage,v 1.1 2000/06/01 21:00:44 gson Exp $
|
||||
Loading…
Reference in a new issue