( commit options

Info Catalog ( commit ( commit examples
 A.10.1 commit options
 These standard options are supported by `commit' ( Common
 options, for a complete description of them):
      Local; run only in current working directory.
      Commit directories recursively.  This is on by default.
      Commit to REVISION.  REVISION must be either a branch, or a
      revision on the main trunk that is higher than any existing
      revision number ( Assigning revisions).  You cannot commit
      to a specific revision on a branch.
    `commit' also supports these options:
      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.
      Note that this is not the standard behavior of the `-f' option as
      defined in  Common 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'.
      Use MESSAGE as the log message, instead of invoking an editor.
Info Catalog ( commit ( commit examples
automatically generated byinfo2html