Java Reference
In-Depth Information
Example 8.3
Checking out a tagged revision
$ cd
$ mkdir fixes
$ cd fixes
$ cvs co -r QA myproject
cvs checkout: Updating myproject
...
U myproject/Account.java
U myproject/Caltron.java
U myproject/Demo.java
U myproject/Employee.java
U myproject/Person.java
...
$ cd myproject
$ cvs status Account.java
===================================================================
File: Account.java Status: Up-to-date
Working revision: 1.2 Sat Oct 26 03:32:17 2002
Repository revision: 1.2 /usr/local/srctree/myproject/Account.java,v
Sticky Tag: QA (branch: 1.2.2)
Sticky Date: (none)
Sticky Options: (none)
$
Now that you have the label set down, you need to check out a copy of
that
version of the source. Since we are checking out a new copy, be sure that
your
CVSROOT
environment variable is set appropriately (see above). Then find
some new directory to put your source and check out a copy with the tag, as
shown in Example 8.3.
We did a
cvs status
after the checkout to show you the important dif-
ference between this version and the other versions. These files will all show a
Sticky Tag
in their status. This is the label used to check out or update this
version of the source. When you check in changes to these source files, the
changes will be against that branch, and not the head.
From there on, everything is the same. Make your changes and just check
files in as usual. CVS will remember (via the files in the
CVS
directory) that
you're on the branch, so when you check things in, they'll go to the branch.
The important thing is to create the tag as a
branch
tag so that you can
commit changes against that branch. The downside, however, is that you now
