ci.1 (2010 09)

c
ci(1) ci(1)
NAME
ci - check in RCS revisions
SYNOPSIS
ci [options ] file...
DESCRIPTION
ci stores new revisions into RCS files. Each file name ending in
,v is treated as an RCS file; all others
are assumed to be working files.
ci
deposits the contents of each working file into the corresponding
RCS file (see rcsintro (5)).
If the RCS file does not exist,
ci creates it and deposits the contents of the working file as the initial
revision. The default number is "1.1". The access list is initialized to empty. Instead of the log message,
ci requests descriptive text (see the -t option below).
An RCS file created by
ci inherits the read and execute permissions from the working file. If the RCS
file exists, ci preserves its read and execute permissions.
ci always turns off all write permissions of
RCS files.
The caller of the command must have read/write permission for the directories containing the RCS file
and the working file, and read permission for the RCS file itself. A number of temporary files are created.
A semaphore file is created in the directory containing the RCS file.
ci always creates a new RCS file
and unlinks the old one; therefore links to RCS files are useless.
For
ci to work, the user’s login must be in the access list unless the access list is empty, the user is the
owner of the file, or the user is super-user.
Normally,
ci checks whether the revision to be deposited is different from the preceding one. If it is not
different, ci either aborts the deposit (if -q is given) or asks whether to abort (if
-q is omitted). A
deposit can be forced with the
-f option.
If sufficient memory is not available for checking the difference between the revision to be deposited and
the preceding one, then either
swap or maxdsiz values can be increased.
For each revision deposited,
ci prompts for a log message. The log message should summarize the
change and must be terminated with a line containing a single "." or a control-D. If several files are being
checked in, ci asks whether or not to reuse the log message from the previous file. If the standard input
is not a terminal, ci suppresses the prompt and uses the same log message for all files (see
-m option
below.
The number of the deposited revision can be given with any of the options
-r, -f
, -k, -l, -u,or -q (see
-r option below).
To add a new revision to an existing branch, the head revision on that branch must be locked by the
caller. Otherwise, only a new branch can 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 can be broken with the
rcs command (see rcs (1)).
Options
-f[rev] Forces a deposit. The new revision is deposited even if it is not different from the preced-
ing one.
-k[rev] Searches the working file for keyword values to determine its revision number, creation
date, author, and state (see co(1)), and assigns these values to the deposited revision,
rather than computing them locally. A revision number given with a command option
overrides the number in the working file. This option is useful for software distribution.
A revision that is sent to several sites should be checked in with the -k option at these
sites to preserve its original number, date, author, and state.
-l[rev] Works like -r, except it performs an additional co -l for the deposited revision. Thus,
the deposited revision is immediately checked out again and locked. This is useful for
saving a revision although one wants to continue editing it after the check-in.
-m"msg" Uses the string msg as the log message for all revisions checked in.
-n"name" Assigns the symbolic name name to the checked-in revision. ci prints an error message
if name is already assigned to another number.
HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1