rcs - change RCS file attributes
rcs [options] file...
Create and initialize a new RCS file, but do not deposit any
revision. If the RCS file has no path prefix, try to place it first into the
./RCS, and then into the
current directory. If the RCS file already exists, print an error message.
Append the login names appearing in the comma-separated list
to the access list of the RCS file.
Append the access list of
to the access list of the RCS file.
Erase the login names appearing in the comma-separated list
from the access list of the RCS file. If
is omitted, erase the entire access list.
Set the default branch to
is omitted, the default branch is reset
to the (dynamically) highest branch on the trunk.
sets the comment leader to
The comment leader is printed before every log message line generated by the
co(1)). This is useful for programming languages without multi-line
comments. An initial
, or an
-c, guesses the comment leader from the
suffix of the working file.
Set the default keyword substitution to
subst. The effect of keyword substitution is described in
Giving an explicit
overrides this default.
is incompatible with
to restore the normal default keyword substitution.
Lock the revision with number
If a branch is given, lock the latest revision on that branch. If
is omitted, lock the latest revision on the default branch.
Locking prevents overlapping changes. A lock is removed with
Unlock the revision with number
If a branch is given, unlock the latest revision on that branch. If
is omitted, remove the latest lock held by the caller. Normally,
only the locker of a revision may unlock it. Somebody else unlocking a revision
breaks the lock. This causes a mail message to be sent to the original locker.
The message contains a commentary solicited from the breaker. The commentary
is terminated by end-of-file or by a line containing
Set locking to
strict. Strict locking
means that the owner of an RCS file is not exempt from locking for checkin.
This option should be used for files that are shared.
Set locking to non-strict. Non-strict locking means that
the owner of a file need not lock a revision for checkin. This option should
be used for files that are shared. Whether default locking
is strict is determined by your system administrator, but it is normally strict.
rev's log message
Associate the symbolic name
with the branch or revision
rev. Delete the symbolic
name if both
otherwise, print an error message if
associated with another number. If
it is expanded before association. A
of a branch number followed by a
stands for the current
latest revision in the branch. A
with an empty
stands for the current latest revision on the default branch,
normally the trunk. For example,
with the current latest revision of all the named RCS files;
this contrasts with
with the revision
numbers extracted from keyword strings in the corresponding working files.
-n, except override any previous
deletes (outdates) the revisions given by
range. A range consisting of a single revision number means that
revision. A range consisting of a branch number means the latest revision
on that branch. A range of the form
on the same branch,
means from the beginning of the
up to and including
means from revision
to the end of the branch
rev. None of the outdated revisions
may have branches or locks.
Run quietly; do not print diagnostics.
Run interactively, even if the standard input is not a terminal.
Set the state attribute of the revision
a branch number, assume the latest revision on that branch. If
is omitted, assume the latest revision on the default branch.
Any identifier is acceptable for
state. A useful
set of states is
(for stable), and
(for released). By default,
sets the state of a revision to
Write descriptive text from the contents of the named
into the RCS file, deleting the existing text. The
pathname may not begin with
is omitted, obtain the text from standard
input, terminated by end-of-file or by a line containing
by itself. Prompt for the text if interaction is possible; see
-i, descriptive text is obtained even if
is not given.
Write descriptive text from the
into the RCS file, deleting the existing text.
Emulate RCS version
to characterize RCS
rcs creates new RCS files or changes attributes of existing ones. An RCS file contains multiple revisions of text, an access list, a change log, descriptive text, and some control attributes. For rcs to work, the caller's login name must be on the access list, except if the access list is empty, the caller is the owner of the file or the superuser, or the -i option is present.
Pathnames matching an RCS suffix denote RCS files; all others denote
working files. Names are paired as explained in
ci(1). Revision numbers
use the syntax described in
The -brev option generates an RCS file that cannot be parsed by RCS version 3 or earlier.
The -ksubst options (except -kkv) generate an RCS file that cannot be parsed by RCS version 4 or earlier.
Use rcs -Vn to make an RCS file acceptable to RCS version n by discarding information that would confuse version n.
RCS version 5.5 and earlier does not support the
option, and requires a
suffix on an RCS pathname.
The separator for revision ranges in the -o option used to be - instead of :, but this leads to confusion when symbolic names contain -. For backwards compatibility rcs -o still supports the old - separator, but it warns about this obsolete use.
Symbolic names need not refer to existing revisions or branches. For
option does not remove symbolic names for
the outdated revisions; you must use
to remove the names.
accesses files much as
that it uses the effective user for all accesses, it does not write the working
file or its directory, and it does not even read the working file unless a
revision number of
options prepended to the argument list, separated by spaces.
The RCS pathname and the revisions outdated are written to the diagnostic
output. The exit status is zero if and only if all operations were successful.
Author: Walter F. Tichy. Revision Number: 220.127.116.11; Release Date: 1993/10/07. Copyright © 1982, 1988, 1989 by Walter F. Tichy. Copyright © 1990, 1991 by Paul Eggert.
co(1), ci(1), ident(1), rcsdiff(1), rcsintro(1), rcsmerge(1), rlog(1), rcsfile(5)
Walter F. Tichy, RCS--A System for Version Control, Software--Practice & Experience 15, 7 (July 1985), 637-654.