Next: [[cvs: commit examples#commit examples|commit examples]], Up: [[cvs: commit--Check files into the repository#commit—Check files into the repository|commit]] |[[cvs: Index#SEC_Contents|Contents]]||[[cvs: Index#Index|Index]]|

----

==== commit options ====

These standard options are supported by `commit` (see [[cvs: Common command options#Common command options|Common options]], for a complete description of them):

;`-l` : Local; run only in current working directory.

;`-R` : Commit directories recursively. This is on by default.

;`-r revision` : Commit to revision. revision must be either a branch, or a revision on the main trunk that is higher than any existing revision number (see [[cvs: Assigning revisions#Assigning revisions|Assigning revisions]]). You cannot commit to a specific revision on a branch.

`commit` also supports these options:

;`-F file` : Read the log message from file, instead of invoking an editor.

;`-f` : Note that this is not the standard behavior of the ‘`-f`’ option as defined in [[cvs: Common command options#Common command options|Common options]].

: Force CVS to commit a new revision even if you haven’t made any changes to the file. If the current revision of file is 1.7, then the following two commands are equivalent:

$ cvs commit -f file $ cvs commit -r 1.8 file

: The ‘`-f`’ option disables recursion (i.e., it implies ‘`-l`’). To force CVS to commit a new revision for all files in all subdirectories, you must use ‘`-f -R`’.

;`-m message` : Use message as the log message, instead of invoking an editor.

This document was generated on a sunny day using [http://www.nongnu.org/texi2html/ texi2html].