For the RCS control system,  Read the following man pages:

	rcsintro
	ci
	co
	rcs

Then see if you can edit the file "src/testing_rcs".  [YOU WILL NEED TO
DO THIS WITH A REAL FILE IN THE RCS DIRECTORY.] You should be
able to do it if you do the following:

	co -l testing_rcs		// this locks the file and
					// allows you to edit it.

		edit the file leaving your mark behind

	ci testing_rcs			// this puts it back

		add some sort of comment to the log

Thats all there is to it!

RCS will keep track of the permissions for us.  So we shouldn't have
as much problems with people not being able to read the files.  But,
be sure that if you create a new file, it has group read permissions
on it.

I've made a directory called ~/src in my home directory (actually my
/button/... directory).  I then 

		ln -s /button/goteam/src/RCS RCS

this made symbolic link to the goteam/src/RCS directory.  Then if I
check out all the files:

		co RCS/*

that will copy (read only) all the files to my ~/src directory.  Then
if I want to modify one, I can

		co -l file_name.cc

and modify it, then check it back in:

		ci file_name.cc

and it should be put back in the goteam/src/RCS directory.  So if
someone else checks out the files they will get the new and improved
file. 

OF COURSE, if you "co -l" a file and don't put it back, no one else
can modify it.

It is useful to define aliases (in your .cshrc file) to see who has locked files:

alias locked   'rlog -L -R RCS/*'

alias locked_me 'rlog -L -R -lungar RCS/*'

The former sees who has locked a file; the latter checks which files user "ungar"
has locked.

> Emacs interfaces to the version control!
> Instead of doing the following to check out a file:
> 
> 	1) try to edit the read only file
> 	2) shit, must check it out
> 	3) go to shell and check out file
> 	4) go back to emacs and find file again
> 	5) say yes to "read in new version on disk"
> 
> All of this anoynace is compressed to the emacs command: ^x v v.
> When you are done, if you didn't change it, ^x v v will revert the
> file.  If you did change it, it will save it for you and ask you for
> the change comment!  All very slick!
>