HP-UX Reference (11i v1 05/09) - 1 User Commands A-M (vol 1)

c
ci(1) ci(1)
-q[rev] Quiet mode; diagnostic output is not printed. A revision that is not different from the
preceding one is not deposited unless -f is given.
-r[rev] Assigns the revision number rev to the checked-in revision, releases the corresponding lock,
and deletes the working file. This is the default.
If rev is omitted,
ci derives the new revision number from the caller’s last lock. If the
caller has locked the head revision of a branch, the new revision is added to the head of
that branch and a new revision number is assigned to the new revision. The new revision
number is obtained by incrementing the head revision number. If the caller locked a non-
head revision, a new branch is started at the locked revision, and the number of the locked
revision is incremented. The default initial branch and level numbers are 1. If the caller
holds no lock, but is the owner of the file and locking is not set to strict, the revision is
added to the head of the trunk.
If rev indicates a revision number, it must be higher than the latest one on the branch to
which rev belongs, or must start a new branch.
If rev indicates a branch instead of a revision, the new revision is added to the head of that
branch. The level number is obtained by incrementing the head revision number of that
branch. If rev indicates a non-existing branch, that branch is created with the initial revi-
sion numbered rev
.1.
NOTE: On the trunk, revisions can be added to the head, but not inserted.
-s"state" Sets the state of the checked-in revision to the identifier state. The default is
Exp.
-t[txtfile] Writes descriptive text into the RCS file (deletes the existing text). If txtfile is omitted,
ci
prompts the user for text from standard input that is terminated with a line containing a
single . or Ctrl-D. Otherwise, the descriptive text is copied from the file txtfile.During
initialization, descriptive text is requested even if
-t is not given. The prompt is
suppressed if standard input is not a terminal.
-u[rev] Similar to -l, except that the deposited revision is not locked. This is useful if one wants
to process (e.g., compile) the revision immediately after check in.
Access Control Lists (ACLs)
Optional ACL entries should not be added to RCS files, because they might be deleted.
DIAGNOSTICS
For each revision, ci prints the RCS file, the working file, and the number of both the deposited and the
preceding revision. The exit status always refers to the last file checked in, and is 0 if the operation was
successful, 1 if unsuccessful.
EXAMPLES
If the current directory contains a subdirectory RCS with an RCS file io.c,v, all of the following com-
mands deposit the latest revision from io.c into RCS/io.c,v :
ci io.c
ci RCS/io.c,v
ci io.c,v
ci io.c RCS/io.c,v
ci io.c io.c,v
ci RCS/io.c,v io.c
ci io.c,v io.c
Check in version 1.2 of RCS file foo.c,v, with the message Bug fix:
ci -r1.2 -m"Bug Fix" foo.c,v
WARNINGS
The names of RCS files are generated by appending ,v to the end of the working file name. If the result-
ing RCS file name is too long for the file system on which the RCS file should reside, ci terminates with
an error message.
The log message cannot exceed 2046 bytes.
A file with approximately 240 revisions may cause a hash table overflow. ci cannot add another revision
to the file until some of the old revisions have been removed. Use the rcs -o (obsolete) command option
Section 1−−92 Hewlett-Packard Company − 2 − HP-UX 11i Version 1: September 2005