Java™ Application Development on Linux - Dator

8.2 Source Control: Whys and Hows209Example 8.3 Checking out a tagged revision$ cd$ mkdir fixes$ cd fixes$ cvs co -r QA myprojectcvs checkout: Updating myproject...U myproject/Account.javaU myproject/Caltron.javaU myproject/Demo.javaU myproject/Employee.javaU 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 2002Repository revision: 1.2 /usr/local/srctree/myproject/Account.java,vSticky 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 ofthat version of the source. Since we are checking out a new copy, be sure thatyour CVSROOT environment variable is set appropriately (see above). Then findsome new directory to put your source and check out a copy with the tag, asshown in Example 8.3.We did a cvs status after the checkout to show you the important differencebetween this version and the other versions. These files will all show aSticky Tag in their status. This is the label used to check out or update thisversion of the source. When you check in changes to these source files, thechanges will be against that branch, and not the head.From there on, everything is the same. Make your changes and just checkfiles in as usual. CVS will remember (via the files in the CVS directory) thatyou’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 cancommit changes against that branch. The downside, however, is that you now