Revision Control System


Revision Control System is an early implementation of a version control system. It is a set of UNIX commands that allow multiple users to develop and maintain program code or documents. With RCS, users can make their own revisions of a document, commit changes, and merge them. RCS was originally developed for programs but is also useful for text documents or configuration files that are frequently revised.

History

Development

RCS was first released in 1982
by Walter F. Tichy at Purdue University. It was an alternative tool to the then-popular Source Code Control System which was nearly the first version control software tool. RCS is currently maintained by the GNU Project.
An innovation in RCS is the adoption of reverse deltas. Instead of storing every revision in a file like SCCS does with interleaved deltas, RCS stores a set of edit instructions to go back to an earlier version of the file. Tichy claims that it is faster for most cases because the recent revisions are used more often.

Legal and licensing

Initially, its license prohibited redistribution without written permission from Walter Tichy:
A READ_ME file accompanied some versions of RCS which further restricted distribution, e.g., in 4.3BSD-Reno.
Ca. 1989, the RCS license was altered to something similar to the contemporary BSD licenses, as seen by comments in the source code.
RCS 4.3, released 26 July 1990, was distributed "under license by the Free Software Foundation", under the terms of the GNU [General Public License|GPL].
OpenBSD provides a different implementation called OpenRCS, which is BSD-licensed.

Behavior

Mode of operation

RCS works well with standalone files and supports multi-file projects but, by modern standards, that support is limited: RCS can assemble the versions of multiple files into a single release but it lacks support for atomic commit across those files. Although it provides branching, the version syntax is cumbersome. Instead of using branches, many teams just use the built-in locking mechanism and work on a single head branch.

Usage

RCS revolves around the usage of "revision groups" or sets of files that have been checked-in via the co and ci commands. By default, a checked-in file is removed and replaced with a ",v" file which can then be checked out by anyone with access to the revision group. RCS files reflect the main file with additional metadata on its first lines. Once checked in, RCS stores revisions in a tree structure that can be followed so that a user can revert a file to a previous form if necessary.

Advantages

Disadvantages

  • There is little security, in the sense that the version history can be edited by the users.
  • Only one user can work on a file at a time.