HP-UX Reference (11i v1 00/12) - 1 User Commands N-Z (vol 2)

__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1/neqn.1
________________________________________________________________
___ ___
r
rcs(1) rcs(1)
NAME
rcs - change RCS file attributes
SYNOPSIS
rcs [options ] file ...
DESCRIPTION
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 user’s
login name must be on the access list, except if the access list is empty, if the user is the owner of the file or
the superuser, or if the -i option is present.
The user of the command must have read/write permission for the directory containing the RCS file and
read permission for the RCS file itself. rcs creates a semaphore file in the same directory as the RCS file
to prevent simultaneous update. For changes, rcs always creates a new file. On successful completion,
rcs deletes the old one and renames the new one. This strategy makes links to RCS files useless.
Files ending in ,v are RCS files; all others are working files. If a working file is given, rcs tries to find
the corresponding
RCS file first in directory ./RCS, then in the current directory, as explained in rcsin-
tro(5).
Options
rcs recognizes the following options:
-alogins Appends the login names appearing in the comma-separated list logins to the access
list of the
RCS file.
-Aoldfile Appends the access list of oldfile to the access list of the RCS file.
-c "string" Sets the comment leader to string. The comment leader is printed before every log
message line generated by the keyword $Log$ during check out (see co(1)). This is
useful for programming languages without multi-line comments. During rcs -i or
initial ci, the comment leader is guessed from the suffix of the working file. Note, a
comment leader is inserted at the beginning of each line of log information. The com-
ment leader is determined by the suffix used with the file name, as in foo.c, or foo.sh,
or foo.p. Note you can specify a different comment leader through the "rcs" command.
The following table shows the comment leader associated with each file name suffix:
SUFFIX FILES Comment Character
c c ’*’
C C Header ’*’
sh shell ’#’
s Assembly ’#’
p pascal ’*’
r ratfor ’#’
e efl ’#’
l lex ’*’
y yacc ’*’
yr yacc-rarfor ’*’
ye yacc-efl ’*’
ml mocklisp ’;’
mac macro ’;’
f fortran ’c’
ms ms-macros ’\’
me me-macros ’\’
"" empty suffix ’#’
nil unknown suffix ’""’
-e[logins]
Erases the login names appearing in the comma-separated list logins from the access list of the
RCS file. If logins is omitted, the entire access list is erased.
-i Creates and initializes a new RCS file, but does not deposit any revision. If the
RCS file has no
path prefix,
rcs tries to place it first into the subdirectory ./RCS, then into the current
Section 1−−766 − 1 − HP-UX Release 11i: December 2000
___
___