A.10.1 commit options

These standard options are supported by commit (see section Common command 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 section Assigning revisions). You cannot commit to a specific revision on a branch.

commit also supports these options:

-c

Refuse to commit files unless the user has registered a valid edit on the file via cvs edit. This is most useful when `commit -c' and `edit -c' have been placed in all `.cvsrc' files. A commit can be forced anyways by either regestering an edit retroactively via cvs edit (no changes to the file will be lost) or using the -f option to commit. Support for commit -c requires both client and a server versions 1.12.10 or greater.

-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 Common command options.

Force CVS to commit a new revision even if you haven't made any changes to the file. As of CVS version 1.12.10, it also causes the -c option to be ignored. 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 September, 14 2007 using texi2html 1.76.