CVS: Concurrent Versioning System

The Example

This example presents the use of CVS by a (perhaps) typical member of UMBC's Telltale group; we'll call him Pete (programmer engaged in Telltale experimentation).

Pete has joined the Telltale group. He must first set his CVSROOT environment variable to point to the source tree.	setenv CVSROOT /home/lait1/src (place in .login, or appropriate location)
Next, he must checkout the code. This creates a copy of the source- tree for telltale, rooted in the current directory, or ~pete/mywork/telltale/	cd ~pete/mywork cvs checkout telltale
Pete decides that, in addition to his modifications, a new file is needed. He must inform CVS.	cvs add newfile.h
After a while, Pete feels he should check in his changes (he should feel this way often). He must: 1. Update his version 2. Check that code is okay, or fix 3. Check in his changes 4. Change group information	(from ~pete/mywork/telltale) cvs update (recompile, debug...) cvs commit (from MST root) chgrp -R telltale telltale

Things to remember:

The CVS -d option can be used to specify the MST.
Avoid more than one person modifying one section of code at same time.
Both cvs itself and the individual subcommands can take arguments. In particular, -d MyCvsRoot is a cvs option, while the -d argument to cvs release is an option to release. cvs -d foo release is a very different command from cvs foo -d release. In the latter case, the subtree will be deleted!

RSC 7/11/96