MPE/iX Shell and Utilities Reference Manual, Vol 1

ci(1) MPE/iX Shell and Utilities ci(1)
If the user has locked the tip revision of a branch, the new revision is appended to
that branch. The new revision number is obtained by incrementing the tip revision
number. If the user locked a non-tip revision, ci starts a new branch at that revision
by incrementing the highest branch number at that revision. The default initial
branch and level numbers are 1.
If you do not specify rev and you have no lock, but you are the owner of the file and
locking is not set to strict, the revision is appended to the default branch (normally
the trunk; see rcs –b).
–sstate
sets the state of the checked-in revision to the identifier state. The default state is
Exp.
–T forces ci to check in the revision using text format. If the revision is actually a non-
text file,
RCS
may not work properly. –T cannot be specified if the RCS file already
contains revisions checked in using binary format or the RCS
file was created with the
rcs –B command.
–t[txtfile]
writes descriptive text into the RCS file (deleting the existing descriptive text). If
txtfile is omitted, ci prompts you for text supplied from the standard input. You may
enter any number of lines of text. When you have finished entering the description,
enter a line containing a single dot (.), the string ˜., or the end-of-file character.
rcsedit(3) describes facilities for editing the descriptive text as you enter it.
If txtfile is specified, the descriptive text is copied from that file. During the initial
check-in of a file, descriptive text is requested even if –t is not given. The prompt is
suppressed if standard input is not a terminal.
–u[rev]
works like –l, except that the checked-in revision is not locked. This is useful if you
want to process (for example, compile) the revision immediately after check-in.
–wlogin
uses login for the author field of the checked in revision. This is useful for altering
the author, and for –k if no author is available.
–Yfile specifies file as the local configuration file.
File Modes
An
RCS file created by ci inherits the read and execute permissions from the working file. If
the RCS file exists already, ci preserves its read and execute permissions. ci normally turns
off all write permissions of RCS files.
1-98 Commands and Utilities