Making a New Module
This is the first step in setting CVS up for your group.

1. Create a directory to hold all the files from the repository
2. Right-click on directory
3. TortoiseCVS menu
4. Make New Module...
5. Add the following in the dialog window:
• Protocol: ssh (:ext:)
• Server: pisa.ucsd.edu
• Port: [leave blank]
• Repository Folder: /cvs/cse125g#
• User Name: [your login]
6. OK

IMPORTANT! Just because you "Added" the files does not mean that they were added to the repository. You must follow through with committing them to the depot in order for them to be added to the server.

Adding A File / Directory
Note: a .cvs directory must be in the directory in order to add a file or directory.
(Tortoise creates this directory -- do not mess with it!)

1. Right-click on file to be added
2. TortoiseCVS menu
3. Add...
4. Check list in Add dialog window
5. OK

IMPORTANT! Just because you "Added" the files does not mean that they were added to the repository. You must follow through with committing them to the depot in order for them to be added to the server.

Committing Changes
This is the step that actually puts your files into the depot on the server.

1. Right-click on file to be checked in
2. CVS Commit
3. Fill in check-in Message box
4. Check list in Changes Made box
5. OK
6. Examine results from check-in attempt
7. OK

Syncing with the Repository
This is how you synchronize your version of the project on your machine with the latest version ("Head Revision") in the depot.

1. Right-click on the directory to be synced
2. CVS Update
3. Examine results from sync attempt
4. OK

IMPORTANT! During integration you should sync the entire depot to before committing. Once synced -- recompile and run the application to ensure that the changes committed to the depot work with your changes. It is very important that you do not check-in broken code.

Things will break! Normally this will happen because a team member forgot to check-in a source file or asset.

Renaming a File / Directory
CVS is keeping track of your files in a laissez-faire way. In other words, if you modify the file or directory name without telling it, it will just assume that the renamed-file is a different file. Therefore, if you want to change a file or directory name for a file in your project, you need to do it through CVS:

1. Right-click on file to be renamed
2. TortoiseCVS
3. Rename...
4. Enter new name
5. OK

IMPORTANT! Just because you "Renamed" the file does not mean that they were renamed in the repository. You must follow through with committing them to the depot in order for them to be changed on the server.

Also, a rename is really just an add of a new file and a delete of the old file. When committing, if you commit only the file you renamed it will only add your new renamed-file, but not delete the old one. You must commit the directory in which the renamed file resides in order to truly delete the old-named file.

In my past experience, there has been a lot of confusion about what exactly goes into the CVS depot / repository. Hopefully this will clear things up.

Visual Studio creates a lot of extra meta-data files for debugging and IDE state for each build configuration of each project. These should not be checked in and will most likely be annoying to deal with if they are (i.e.: one team member checks in the user options file customized to his / her liking and now when people sync to the depot they're IDE will be set up the same way. This ended up happening last year and people just ended up keeping the files permanently checked out -- hacky solution in the light of ignorance.)

Simply put, please be aware of the files you are checking in.