ci

Check in revisions. ci stores the contents of the specified working files into their corresponding RCS files. Normally, ci deletes the working file after storing it. If no RCS file exists, the working file is an initial revision. In this case, the RCS file is created, and you are prompted to enter a description of the file. If an RCS file exists, ci increments the revision number and prompts you to enter a message that logs the changes made. If a working file is checked in without changes, the file reverts to the previous revision.

The two mutually exclusive options -u and -l , along with -r , are the most common. Use -u to keep a read-only copy of the working file (for example, so the file can be compiled or searched). Use -l to update a revision and then immediately check it out again with a lock. This allows you to save intermediate changes but continue editing (for example, during a long editing session). Use -r to check in a file with a different release number. ci accepts the standard options -q , -V , -V n , -T , -x , and -z .

Options

-d [date ]

Check the file in with a timestamp of date or, if no date is specified, with the time of last modification.

-f [R ]

Force a check-in even if there are no differences.

-i [R ]

Initial check-in, report an error if the RCS file already exists.

-I [R ]

Interactive mode; prompt user even when standard input is not a terminal (e.g., when ci is part of a command pipeline).

-j [R ]

Just check in and do not initialize. Report an error if the RCS file does not already exist.

-k [R ]

Assign a revision number, creation date, state, and author from keyword values that were placed in the working file, instead of computing the revision information from the local environment. -k is useful for software distribution: the preset keywords serve as a timestamp shared by all distribution sites.

-l [R ]

Do a co -l after checking in. This leaves a locked copy of the next revision.

-m msg

Use the msg string as the log message for all files checked in. When checking in multiple files, ci normally prompts whether to reuse the log message of the previous file. -m bypasses this prompting.

-M [R ]

Set the working file's modification time to that of the retrieved version. Use of -M can confuse make and should be used with care.

-n name

Associate a text name with the new revision number.

-N name

Same as -n , but override a previous name .

-r R

Check the file in as revision R .

-r

Without a revision number, -r restores the default behavior of releasing a lock and removing the working file. It is intended to override any default -l or -u set up by aliases or scripts. The behavior of -r in ci is different from most other RCS commands.

-s state

Set the state of the checked-in revision.

-t file

Replace RCS file description with contents of file . This works only for initial check-in.

-t- string

Replace RCS file description with string . This works only for initial check-in.

-u [R ]

Do a co -u after checking in. This leaves a read-only copy.

-w user

Set the author field to user in the checked-in revision.

Examples

Check in chapter files using the same log message:

ci -m'First round edits' chap*

Check in edits to prog.c , leaving a read-only copy:

ci -u prog.c

Start revision level 2; refer to revision 2.1 as "Prototype":

ci -r2 -nPrototype prog.c