Next: , Previous: , Up: Usage   [Contents][Index]

2.2 Invoking ci

rcs ci [options] file …
(or “ci” instead of “rcs ci”)

The ci command adds a revision to the RCS file reflecting the current state of the working file. This operation is also known as “checkin”.


Force new entry, even if no content changed.


See Misc common options.


Initial checkin; error if the RCS file already exists.


Just checkin, don’t initialize; error if the RCS file does not exist.


Compute revision from working file keywords.


Release lock and delete working file.


Do normal checkin.


Like -r, but immediately checkout locked (co -l) afterwards.


Like -l, but checkout unlocked (co -u).


Reset working file mtime (relevant for -l, -u).

Multiple flags in -{fiIjklMqru} may be given, except for -r, -l, -u, which are mutually exclusive. For a fully specified revision of the form br.n, n must be greater than any existing on br, or br must be new. If rev is omitted, compute it from the last lock (co -l), perhaps starting a new branch. If there is no lock, use defbr.(L+1). See Revision options.


See Date option. If no date specified, use the working file modification time.


Use msg as the log message. See Log message option.


Assign symbolic name to the entry. For -n, name must be new (no previous assignment). For -N, overwrite any previous assignment.


See Misc common options. Set the state.


See Description option.


Set the RCS file’s modification time to the new revision’s time if the former precedes the latter and there is a new revision; preserve the RCS file’s modification time otherwise.


Use who as the author.


See Misc common options.

Next: , Previous: , Up: Usage   [Contents][Index]