HP-UX Reference (11i v2 03/08) - 1 User Commands N-Z (vol 2)
r
rcs(1) rcs(1)
-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
directory. If the
RCS file already exists, an error message is printed.
-l[ rev ]
Locks the revision with number rev. If a branch is given, the latest revision on that branch is
locked. If rev is omitted, the latest revision on the trunk is locked. Locking prevents overlap-
ping changes. A lock is removed with ci
or rcs -u (see below).
-L Sets locking to strict. Strict locking means that the owner of an
RCS file is not exempt from
locking for check in. This option should be used for files that are shared.
-nname[:[ rev ]]
Associates the symbolic name name with the branch or revision rev.
rcs prints an error
message if name is already associated with another number. If rev is omitted, the symbolic
name is associated with the latest revision on the trunk. If
:rev is omitted, the symbolic name
is deleted.
-Nname[:[ rev ]]
Same as -n, except that it overrides a previous assignment of name.
-orange
Deletes ("obsoletes") 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 rev1−rev2 means revisions rev1 to rev2 on the same
branch,
-rev means from the beginning of the branch containing rev up to and including rev,
and rev
- means from revision rev to the head of the branch containing rev. None of the out-
dated revisions can have branches or locks.
-q Quiet mode; diagnostics are not printed.
-sstate[:rev ]
Sets the state attribute of the revision rev to state.Ifrev is omitted, the latest revision on the
trunk is assumed. If rev is a branch number, the latest revision on that branch is assumed.
Any identifier is acceptable for state. A useful set of states is Exp
(for experimental), Stab
(for stable), and Rel (for released). By default, ci sets the state of a revision to Exp
.
-t [ txtfile ]
Writes descriptive text into the RCS file (deletes the existing text). If txtfile is omitted,
rcs
prompts the user for text supplied from the standard input, terminated with a line containing
a single . or Ctrl-D. Otherwise, the descriptive text is copied from the file txtfile. If the
-i
option is present, descriptive text is requested even if -t is not given. The prompt is
suppressed if the standard input is not a terminal.
-u [ rev ]
Unlocks the revision with number rev. If a branch is given, the latest revision on that branch
is unlocked. If rev is omitted, the latest lock held by the user is removed. 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 with a line containing a single . or
Control-D.
-U Sets locking to non-strict. Non-strict locking means that the owner of a file need not lock a
revision for check in. This option should not be used for files that are shared. The default (-L
or -U) is determined by the system administrator.
Access Control Lists (ACLs)
Do not add optional
ACL entries to an RCS file, because they are deleted when the file is updated. The
resulting access modes for the new file might not be as desired.
DIAGNOSTICS
The
RCS filename and the revisions outdated are written to the diagnostic output. The exit status always
refers to the last RCS file operated upon, and is 0 if the operation was successful; 1 if unsuccessful.
EXAMPLES
Add the names
jane, mary, dave, and jeff to the access list of RCS file vision,v:
Section 1−−732 Hewlett-Packard Company − 2 − HP-UX 11i Version 2: August 2003