 |
||
 |
||
 |
||
 |
||
 |
||
 |
||
 |
||
 |
||
WARNING: This information has not been updated since October, 1997!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
INDEX ENTRY FOR RCS:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Name: RCS - The Revision Control System
Version: 5.7
Author(s): RCS <rcs-bugs@cs.purdue.edu>
Walter F. Tichy
Paul Eggert
Ftp source: ftp.cs.purdue.edu:/pub/RCS/rcs.tar.Z
Description:
The Revision Control System (RCS) manages multiple revisions of files.
RCS automates the storing, retrieval, logging, identification, and merg-
ing of revisions. RCS is useful for text that is revised frequently,
for example programs, documentation, graphics, papers, and form letters.
The basic user interface is extremely simple. The novice only needs to
learn two commands: ci(1) and co(1). ci, short for "check in", deposits
the contents of a file into an archival file called an RCS file. An RCS
file contains all revisions of a particular file. co, short for "check
out", retrieves revisions from an RCS file.
-- Quoted from the rcsintro manpage by Walter F. Tichy included in
the RCS 5.7 distribution.
Advertised architectures: None listed
RCS + GNU diff will run on any host that conforms to Posix.1.
Prerequisites: C compiler and a diff that supports the -n option;
GNU diff is recommended, since it is much faster and it works with
binary files.
