MPE/iX Shell and Utilities Reference Manual, Vol 1

ci(1) MPE/iX Shell and Utilities ci(1)
NAME
ci — check in a file under RCS
SYNOPSIS
ci [–B][–ddate][–Ffile...][–f[rev]] [–G][–g][–h[rev]] [–I][–k[rev]]
[–l[rev]] [–mmsg][–Nname][–nname][–O][–q[rev]] [–Rdiff_exec]
[–r[rev]] [–sstate][–T][–t[txtfile]] [–u[rev]] [–wlogin][–Yfile] file ...
DESCRIPTION
Note: The
MPE/iX implementation of this utility does not function exactly as this man page
describes. For details, see the MPE/iX NOTES section at the end of this man page.
ci adds a new revision of a working file to the corresponding RCS file. Executing this com-
mand on a file is referred to as checking in the file.
For ci to work, the user’s login name must be on the access list, except if the access list is
empty or the user is the system administrator or the owner of the file. To append a new revi-
sion to an existing branch, the tip revision on that branch must be locked by the user; other-
wise, a new branch must be created. This restriction is not enforced for the owner of the file,
unless locking is set to strict (see rcs(1)). A lock held by someone else may be broken with
the rcs command.
Normally, ci checks whether the revision to be checked in is different from the preceding
one. If it is not different, ci either aborts the check-in (if –q is given) or asks whether to
abort (if –q is omitted). A check-in can be forced with the –f option.
For each revision checked in, ci prompts for a log message. The log message should summa-
rize the change and must be terminated with a line consisting of a single dot (.), the string ˜.,
or an end of file. Log messages may be edited using the facilities described in rcsedit(3).
If several files are checked in, ci asks whether to reuse the previous log message. If the stan-
dard input is not a terminal, ci suppresses the prompt and uses the same log message for all
files. See also –m.
The number of the checked-in revision can be given by any of the options –r, –f, –k, –l, –u,
–h,or–q.
If the
RCS file does not exist, ci creates it and checks in the contents of the working file as the
initial revision. The default number for this revision is 1.1, and the access list is initialized
to empty. Instead of the log message, ci requests descriptive text (see –t). This descriptive
text may be edited using the facilities described in rcsedit(3). If you specify the -r
option, you are asked for both descriptive text and a log message.
If the configuration file specifies Compress, ci compresses the RCS file after the revision has
been checked in. It is not necessary to specify anything about compression when you check it
Commands and Utilities 1-95