Before you proceed
Before you proceed, however, Table 29-5 lists a few terms that will be used throughout the chapter.
Because they are used so frequently, I want to make sure you understand their meaning insofar as
RCS and version control in general are concerned.
Version Control Terms
| Term | Description |
| Lock | A working file retrieved for editing such that no one else can edit it simultaneously. A working file is locked by the first user against edits by other users. |
| RCS file | Any file located in an RCS directory, controlled by RCS, and accessed using RCS commands. An RCS file contains all versions of a particular file. Typically, an RCS file has a ,v extension. |
| Revision | A specific, numbered version of a source file. Revisions begin with 1.1 and increase incrementally, unless forced to use a specific revision number. |
| Working file | One or more files retrieved from the RCS source code repository (the RCS directory) into the current working directory and available for editing. |
RCS manages multiple versions of files, usually but not necessarily source code files. It automates
file version storage and retrieval, change logging, access control, release management, and revision
identification and merging. As an added bonus, RCS minimizes disk space requirements because it
tracks only file changes.
One of RCS's attractions is its simplicity. With only a few commands, you can accomplish a
great deal.