The Revision Control System (RCS) manages multiple revisions of files. RCS automates the storing, retrieval, logging, identification, and merging of revisions. RCS is useful for text that is revised frequently, including source code, programs, documentation, graphics, papers, and form letters.
RCS design is an improvement from its predecessor Source Code Control System (SCCS) (see GNU CSSC). The improvements include an easier user interface and improved storage of versions for faster retrieval. RCS improves performance by storing an entire copy of the most recent version and then stores reverse differences (called "deltas"). RCS uses GNU Diffutils to find the differences between versions.
Latest release: 5.9.4 (2015-01-22)
portability fix in
"make check" for OSX
We now avoid ‘
head -N’, where N is a number, since that
construct is not portable. See:
rcs -o’ better
It seems the term
"outdate" is itself outdated, nowadays (sigh).
This command is now indexed under
@cindex’ before ‘
@item’ in tables
The tables of substitution mode options and common options are now indexed such that selecting the indexed item in Emacs leaves point on the item's line and not the one after.
new index entries
For concepts (locking, implicit checkout, branching-related stuff) and keywords.
introspective stuff moved into chapter
These former chapters have been moved into chapter
"Reporting bugs". As a nice
side-effect, the table of contents of the PDF now is one page.
RCS_MEM_LIMIT’ on manpages updated
RCS 5.9.2 (released 2013-11-28) changed how ‘
works. The Texinfo docs were updated but not the manpages.
GNU Automake 1.15 GNU gnulib 2015-01-20 09:09:03 GNU texinfo 5.2
GNU Autoconf 2.69
Documentation for RCS is available online, as is documentation for most GNU software. You may also find more information about RCS by running info rcs or by looking at /usr/share/doc/rcs/, /usr/local/doc/rcs/, or similar directories on your system.
RCS has the following mailing lists:
Security reports that should not be made immediately public can be sent directly to the maintainer. If there is no response to an urgent issue, you can escalate to the general security mailing list for advice.
Development of RCS, and GNU in general, is a volunteer effort, and you can contribute. For information, please read How to help GNU. If you'd like to get involved, it's a good idea to join the discussion mailing list (see above).
RCS is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
The Free Software Foundation is the principal organizational sponsor of the GNU Operating System. Support GNU and the FSF by buying manuals and gear, joining the FSF as an associate member, or making a donation, either directly to the FSF or via Flattr.