...or RCS as it's better known.
Widely-used source code tool available for most operating systems. Less powerful than the Concurrent Versions System (CVS) and far behind Distributed Version Control for workgroups. However, for a personal repository, it's trivial to set up and use.
RCS makes it easy to get started with version control on your private files. But if you have already gone through the pains of learning CVS, don't bother with RCS.
The primary weakness of RCS is when you are working in a workgroup. When someone locks a file, no one else can make changes to the repository version until you check it back in, you release the lock, or someone steals the lock. For anything but a small group, file locking issues get in the way of getting things done. CVS sidesteps this issue nicely.
The Awki Wiki uses RCS as a backend to provide version control, diffs and history.
RCS tips
mkdir RCS
First, make an RCS directory in your working directory. This keeps all the RCS files tucked neatly away.
ci ''filename'' #ci stands for <c>heck <i>n.
The first time you issue this command for a file, RCS does the following:
Adds the file named filename to your RCS repository.
Removes the original file from your working directory.
Prompts you for a file description for the RCS log.
co ''filename'' #co stands for <c>heck <o>ut.
A copy of the repository file is placed in your working directory. Once you do this, you can view it, compile with it, even alter it. However, if you're planning on checking the file back in again, you may want to use the following command:
co -l ''filename'' #check out and lock.
This has the additional effect of 'locking' the repository. No one but you can check the file back in until the lock is released.
Let's say you make changes to the file and want to check it back in. You can use one of these commands.
ci ''filename'' # Check in the file. Working copy disappears. ci -l ''filename'' # Check in the file. Working copy retained. Lock is retained. ci -u ''filename'' # Check in the file. Working copy retained. Lock is released.
When you check the file back in, RCS asks for a "change log entry". This should be a description of the changes you made. See Good Change Log Entry for discussion on that ball of worms.
---- Additional tips: See Rcs Keywords
Contributors: Anders Bengtsson, Sean Oleary, Chris Garrod
See original on c2.com 