Guys,

I think I've gotten most everything up and working in CVS now.  All cvs
commits will send an email out to me for now, and I'll summarize for the
group, to prevent loads of messages from going out to you guys.  Here is
what you'll need to know to get things up and working (all commands need
to be run on turing):

You need to add the following files to you .cshrc file:

setenv CVSROOT /home/rsims/repo
setenv CVS_RSH ssh
setenv EDITOR emacs (except steve, this is where you put pico .. hehehe)
setenv VISUAL emacs (again steve - pico)

Once you do that you either need to logout and log back in or type:

source ~/.cshrc

This will set you up to use the cvs repository.  I suggest that you make a
directory where you will keep all your checked out tree.  Like ~/src or
something.  Anyway whatever that directory is go there and type this:

cvs co GateBuilder

I gave our project a preliminary name of gatebuilder, we can change it
later.  Anyway you should see the following on your screen:

cvs checkout: Updating GateBuilder
U GateBuilder/README.txt

If you don't see that send me an email because I may not have the
permissions set correctly.  If you do see that then when you cd into the
GateBuilder directory you will see a file called README.txt.  This is
currently the only file in our project.  You can make changes to that file
using any editor.  Once you have made changes type:

cvs commit

to commit any changes into the cvs repository so that everyone else will
be able to "see" your changes.  You may add files by using the command:

cvs add  ...
 
The files will be queued for adding but not added until you type cvs
commit.  To remove a file you need to actually remove the file from your
"working copy" of the tree

rm  ...

You then need to remove the file from the repository with:

cvs remove  ...

The files won't actually be removed from the repository until you type cvs
commit.  In order to "see" any changes that have been commited by others
you need the command:

cvs update

This will only retrieve all updated files.  If new directories have been
added you will need to add a -d to the update.  In fact all updates should
be of this form:

cvs update -d

That should be about everything you need to get started.  Chapters
2,4,6,8,9 and 10 of "Open Source Development with CVS" can be found online
at http://cvsbook.redbean.com  This contains just about everything you'll
need to know to use cvs effectively.  I don't think that we'll be doing
too much branching and what not, so don't get too involved in that.

Ray