Add a glossary entry for "RCS" with a short description of what it can

do, and a few of the reasons why it's still in use today (simple
setup, ubiquitous, etc).

Triggered by:   A discussion with other doc-people
                and Walt Pawley, walt at wump.org.
This commit is contained in:
Giorgos Keramidas 2010-05-07 06:49:32 +00:00
parent 0402e26824
commit 11930f2cee
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=35716

View file

@ -1561,6 +1561,27 @@
</glossdef>
</glossentry>
<glossentry id="rcs-glossary">
<glossterm>Revision Control System</glossterm>
<acronym>RCS</acronym>
<glossdef>
<para>The <emphasis>Revision Control System</emphasis>
(<acronym>RCS</acronym>) is one of the oldest software suites
that implement <quote>revision control</quote> for plain
files. It allows the storage, retrieval, archival, logging,
identification and merging of multiple revisions for each
file. RCS consists of many small tools that work together.
It lacks some of the features found in more modern revision
control systems, like CVS or Subversion, but it is very simple
to install, configure, and start using for a small set of
files. Implementations of RCS can be found on every major
UNIX-like OS.</para>
<glossseealso otherterm="cvs-glossary">
<glossseealso otherterm="svn-glossary">
</glossdef>
</glossentry>
<glossentry id="rd-glossary">
<glossterm>Received Data</glossterm>
<acronym>RD</acronym>