How to use CVS

First of all, you need to set your CVSROOT environment variable to /export/ws06afsr/src/. (you could put the line export CVSROOT=/export/ws06afsr/src/ in your ~/.bash_profile if you're using bash).

Also, commit s don't seem to work if you're working from login.clsp.jhu.edu. You shouldn't be working there anyway - it works fine if you ssh to one of the linux boxes x[0-9[0-9].

Getting a working copy

This can be done with cvs checkout module where module is the name of the module you want. So you could cd to your own directory and run cvs checkout parallel to get the latest parallel training scripts. The current list of modules is given below.

Getting other people's updates

If you know someone else has put an update into CVS, you'll want that latest version. To update your local copy of a module, cd to the directory containing the module and run cvs update. To update only specific files use cvs update filename.

Putting your own updates in

Go to the directory containing your changes and hit cvs commit. Again, to commit only some files use cvs commit filename.

Adding new files

To add a new file to the CVS repository, copy the file to appropriate location in your local copy of the module, and then do cvs add filename

Current modules

The following modules are currently in CVS:

• bin - gmtk binaries
• parallel - parallel EM training and decoding scripts
• triangulateGA_SGE - ChrisBartels' script for gmtk triangulation with a genetic algorithm, modified to work in GridEngine^?
• tksrc
• gmtk_include

There's more on theJHU site and lots more in the original docs.

-- ParthaLal - 10 Jul 2006