These are the notes I made for class today.  They're somewhat documented.
Feel free to send me questions.

-Jeff
====================================================================
CVSROOT = /u/cs190_project/force/cvs/

CVSEDITOR will be spawned when it is time to log a message - pico works well
          for this

----------

In the project directory:  (force == /u/cs190_project/force)

  force
    |
    |-bin
    |-cvs
    |  |
    |  |-CVSROOT
    |  |-force
    |      |-docs
    |      |-include
    |      |-man
    |      |-src
    |         |-your code goes here
    |
    |-lib
    |-data
    |-man

==========================
a sample session:

1) you might want to work in a "working directory" to make sure nothing is
   overwritten/deleted

2) check out your section of the code

> cvs checkout force/src/graph
cvs checkout: Updating force/src/graph

> ls
force

> cd force/src/graph

> ls
yoda.h

3) do whatever work you need to do in your source files, testing them, etc.

4) when they work, commit your changes to the repository

> cvs commit yoda.h

5) this will spawn your CVSEDITOR and allow you to log your changes.  include
   the area of code you changed ("the node insert routine") and the functional
   change you made ("doesn't delete the node inserted")

6) you need to leave the lab so it is time to clean up after yourself

> cd ../../.. (the directory containing "force")

> cvs release -d force
You have [0] altered files in this repository.
Are you sure you want to release (and delete) directory `force/': y

7) you're all good.  0 files were altered since they match the ones in the
   repository (because your change was comitted)

======================
if you need to add a .C or .H file, use:

> cvs add yoda.h (tell CVS to control this file)
...

> cvs commit yoda.h (commit the contents of this file to the repository)

======================
if you need to remove a .C or .H file, use:

> rm yoda.h

> cvs remove yoda.h  (if you don't rm it first, CVS will tell you to)

======================
about binary files:

don't add your .o files to the repository!  this is icky!  cvs will support
binary files, so it won't complain if you try, but this is generally a bad
idea since it makes the checkout/commit process nasty.  libraries go in the
lib directory above the cvs directory, as do builds of the program.  docs
and man pages and shared header files however, _are_ under source control
and should exist in the docs, man, and include directories under the cvs
directory respectively.