Simple RCS Usage

There are 3 things you need to know in order to get going with RCS:

1. Setting up: You need to create a subdirectory named RCS in each directory in which you are maintaining code. Then "check in" (see below) each relevant file.

2. Checking files out: Check files out when you want to start modifying them. The command is:

   co -l <file1> <file2> ....

3. Checking files in: Check files in when you have finished editing them for the time being. Checking in saves the current state of the files, and sets file permissions to "read only". The command is:

   ci -u <file1> <file2> ....

Note: if you use the xemacs editor, you can also check out and in from the "Tools->VC" menu in this editor.

---

If you want to contribute your code to AMMA or GAMA, what happens is:

• You tell the Software Manager
• He copies your RCS directory to the appropriate place, & tells you where this is.
• You dispose of your RCS directory, and do a soft link to the copied version.
• Carry on as before.

---

Other info on RCS:

• man pages on rcs, ci and co
• RCS FAQs
• All you ever wanted to know about RCS
• How Charles Galambos has hacked RCS. (You get the hacked version by default.)