Contents / Previous / Next

commit: Check Files into the Repository

Use `commit' when you want to incorporate changes from your working source files into the source repository. 
 commit [-lnRf] [-m 'log_message' | -F file] 
        [-r revision] [files...]

Commit Options: 

`-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.

`-m MESSAGE'
     Use MESSAGE as the log message, instead of invoking an editor.


Assigning Revisions with commit

By default, CVS will assign numeric revisions by leaving the first number the same and incrementing the second number. For example, `1.1', `1.2', `1.3', etc.

When adding a new file, the second number will always be one and the first number will equal the highest first number of any file in that directory. For example, the current directory contains files whose highest numbered revisions are `1.7', `3.1', and `4.12', then an added file will be given the numeric revision `4.1'.

If you want to set the numeric revisions, you may use the `-r' option to the command cvs commit. For example, to bring all your files up to revision 3.0 (including those that have not changed), invoke: 

  cvs commit -r 3.0
The number you specify must be larger than any existing revision number.