Revision Control System

From Wikipedia, the free encyclopedia
Jump to: navigation, search
For revision control systems in general, see Revision control.
Revision Control System
Original author(s) Walter F. Tichy
Developer(s) GNU Project
Initial release 1982; 32 years ago (1982)
Stable release 5.9.2[1] / November 29, 2013; 9 months ago (2013-11-29)
Written in C
Operating system Unix-like
Type Revision control
License GNU General Public License

The Revision Control System (RCS) is a software implementation of revision control that automates the storing, retrieval, logging, identification, and merging of revisions. RCS is useful for text that is revised frequently, for example programs, documentation, procedural graphics, papers, and form letters. RCS is also capable of handling binary files, though with reduced efficiency. Revisions are stored with the aid of the diff utility.


RCS was first released in 1982[2] [3] by Walter F. Tichy while he was at Purdue University as a free alternative to the then-popular Source Code Control System (SCCS). It is now part of the GNU Project, which is still maintaining it.

Mode of operation[edit]

RCS operates only on single files; it has no way of working with an entire project. Although it provides branching for individual files, 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.


Concurrent Versions System (CVS)[edit]

A simple system called CVS was developed capable of dealing with RCS files en masse, and this was the next natural step of evolution of this concept, as it “transcends but includes” elements of its predecessor. CVS was originally a set of scripts which used RCS programs to manage the files. It no longer does that; rather, it operates directly on the files.

Project Revision Control System (PRCS)[edit]

A later, higher-level system, PRCS[4] uses RCS-like files, but was never simply a wrapper. In contrast to CVS, PRCS improves the delta compression of the RCS files using Xdelta.


In single-user scenarios, such as server configuration files or automation scripts, RCS may still be the preferred revision control tool as it is simple and no central repository needs to be accessible for it to save revisions. This makes it a more reliable tool when the system is in dire maintenance conditions. Additionally, the saved backup files are easily visible to the administration so the operation is straightforward. However, there are no built-in tamper protection mechanisms (that is, users who can use the RCS tools to version a file also, by design, are able to directly manipulate the corresponding version control file) and this is leading some security conscious administrators to consider client/server version control systems that restrict users' ability to alter the version control files.[citation needed]


Some wiki engines, including TWiki and Foswiki, use RCS for storing page revisions.


  1. ^ "GNU RCS 5.9.2 available". 2013-11-29. Retrieved 2013-11-29. 
  2. ^ "RCS man page". Retrieved 2010-02-07. 
  3. ^ Tichy, Walter (1982). "Design, implementation, and evaluation of a Revision Control System". ICSE '82 Proceedings of the 6th international conference on Software engineering: 58–67. Retrieved 12 June 2012. 
  4. ^ MacDonald, Joshua P (May 9, 2004). "PRCS, the Project Revision Control System". Retrieved 2008-12-12. 

External links[edit]