| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This appendix describes the overall structure of CVS commands, and describes some commands in detail (others are described elsewhere; for a quick reference to CVS commands, see section B. Quick reference to CVS commands).
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The overall format of all CVS commands is:
cvs [ cvs_options ] cvs_command [ command_options ] [ command_args ] |
cvs
cvs_options
cvs_command
command_options
command_args
There is unfortunately some confusion between
cvs_options and command_options.
`-l', when given as a cvs_option, only
affects some of the commands. When it is given as a
command_option is has a different meaning, and
is accepted by more commands. In other words, do not
take the above categorization too seriously. Look at
the documentation instead.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
CVS can indicate to the calling environment whether it succeeded or failed by setting its exit status. The exact way of testing the exit status will vary from one operating system to another. For example in a unix shell script the `$?' variable will be 0 if the last command returned a successful exit status, or greater than 0 if the exit status indicated failure.
If CVS is successful, it returns a successful status;
if there is an error, it prints an error message and
returns a failure status. The one exception to this is
the cvs diff command. It will return a
successful status if it found no differences, or a
failure status if there were differences or if there
was an error. Because this behavior provides no good
way to detect errors, in the future it is possible that
cvs diff will be changed to behave like the
other CVS commands.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
There are some command_options that are used so
often that you might have set up an alias or some other
means to make sure you always specify that option. One
example (the one that drove the implementation of the
`.cvsrc' support, actually) is that many people find the
default output of the `diff' command to be very
hard to read, and that either context diffs or unidiffs
are much easier to understand.
The `~/.cvsrc' file is a way that you can add
default options to cvs_commands within cvs,
instead of relying on aliases or other shell scripts.
The format of the `~/.cvsrc' file is simple. The
file is searched for a line that begins with the same
name as the cvs_command being executed. If a
match is found, then the remainder of the line is split
up (at whitespace characters) into separate options and
added to the command arguments before any
options from the command line.
If a command has two names (e.g., checkout and
co), the official name, not necessarily the one
used on the command line, will be used to match against
the file. So if this is the contents of the user's
`~/.cvsrc' file:
log -N diff -u update -P checkout -P |
the command `cvs checkout foo' would have the `-P' option added to the arguments, as well as `cvs co foo'.
With the example file above, the output from `cvs
diff foobar' will be in unidiff format. `cvs diff
-c foobar' will provide context diffs, as usual.
Getting "old" format diffs would be slightly more
complicated, because diff doesn't have an option
to specify use of the "old" format, so you would need
`cvs -f diff foobar'.
In place of the command name you can use cvs to
specify global options (see section A.4 Global options). For
example the following line in `.cvsrc'
cvs -z6 |
causes CVS to use compression level 6.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The available `cvs_options' (that are given to the left of `cvs_command') are:
--allow-root=rootdir
-a
-b bindir
-T tempdir
$TMPDIR environment
variable and any precompiled directory. This parameter should be
specified as an absolute pathname.
-d cvs_root_directory
$CVSROOT environment variable. See section 2. The Repository.
-e editor
$CVSEDITOR and $EDITOR
environment variables. For more information, see
1.3.2 Committing your changes.
-f
-H
--help
-l
-n
Note that CVS will not necessarily produce exactly the same output as without `-n'. In some cases the output will be the same, but in other cases CVS will skip some of the processing that would have been required to produce the exact same output.
-Q
-q
-r
$CVSREAD environment variable is set
(see section D. All environment variables which affect CVS). The default is to
make working files writable, unless watches are on
(see section 10.6 Mechanisms to track who is editing files).
-s variable=value
-t
-v
--version
-w
$CVSREAD environment variable.
Files are created read-write by default, unless $CVSREAD is
set or `-r' is given.
-x
-z gzip-level
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This section describes the `command_options' that are available across several CVS commands. These options are always given to the right of `cvs_command'. Not all commands support all of these options; each option is only supported for commands where it makes sense. However, when a command has one of these options you can almost always count on the same behavior of the option as in other commands. (Other command options, which are listed with the individual commands, may have different behavior from one CVS command to the other).
Warning: the `history' command is an exception; it supports many options that conflict even with these standard options.
-D date_spec
The specification is sticky when you use it to make a private copy of a source file; that is, when you get a working file using `-D', CVS records the date you specified, so that further updates in the same directory will use the same date (for more information on sticky tags/dates, see section 4.9 Sticky tags).
`-D' is available with the checkout,
diff, export, history,
rdiff, rtag, and update commands.
(The history command uses this option in a
slightly different way; see section A.11.1 history options).
A wide variety of date formats are supported by CVS. The most standard ones are ISO8601 (from the International Standards Organization) and the Internet e-mail standard (specified in RFC822 as amended by RFC1123).
ISO8601 dates have many variants but a few examples are:
1972-09-24 1972-09-24 20:05 |
There are a lot more ISO8601 date formats, and CVS accepts many of them, but you probably don't want to hear the whole long story :-).
In addition to the dates allowed in Internet e-mail itself, CVS also allows some of the fields to be omitted. For example:
24 Sep 1972 20:05 24 Sep |
The date is interpreted as being in the local timezone, unless a specific timezone is specified.
These two date formats are preferred. However, CVS currently accepts a wide variety of other date formats. They are intentionally not documented here in any detail, and future versions of CVS might not accept all of them.
One such format is
month/day/year. This may
confuse people who are accustomed to having the month
and day in the other order; `1/4/96' is January 4,
not April 1.
Remember to quote the argument to the `-D' flag so that your shell doesn't interpret spaces as argument separators. A command using the `-D' flag can look like this:
$ cvs diff -D "1 hour ago" cvs.texinfo |
-f
Note that even with `-f', a tag that you specify must exist (that is, in some file, not necessary in every file). This is so that CVS will continue to give an error if you mistype a tag name.
`-f' is available with these commands:
annotate, checkout, export,
rdiff, rtag, and update.
Warning: The commit and remove
commands also have a
`-f' option, but it has a different behavior for
those commands. See A.8.1 commit options, and
7.2 Removing files.
-k kflag
checkout or update commands,
CVS associates your selected kflag with the
file, and continues to use it with future update
commands on the same file until you specify otherwise.
The `-k' option is available with the add,
checkout, diff, import and
update commands.
-l
Warning: this is not the same as the overall `cvs -l' option, which you can specify to the left of a cvs command!
Available with the following commands: annotate, checkout,
commit, diff, edit, editors, export,
log, rdiff, remove, rtag,
status, tag, unedit, update, watch,
and watchers.
-m message
Available with the following commands: add,
commit and import.
-n
Warning: this is not the same as the overall `cvs -n' option, which you can specify to the left of a cvs command!
Available with the checkout, commit, export,
and rtag commands.
-P
-p
checkout and update commands.
-R
Available with the following commands: annotate, checkout,
commit, diff, edit, editors, export,
rdiff, remove, rtag,
status, tag, unedit, update, watch,
and watchers.
-r tag
tag or rtag command, two special tags are
always available: `HEAD' refers to the most recent version
available in the repository, and `BASE' refers to the
revision you last checked out into the current working directory.
The tag specification is sticky when you use this
with checkout or update to make your own
copy of a file: CVS remembers the tag and continues to use it on
future update commands, until you specify otherwise (for more information
on sticky tags/dates, see section 4.9 Sticky tags).
The tag can be either a symbolic or numeric tag, as described in 4.4 Tags--Symbolic revisions, or the name of a branch, as described in 5. Branching and merging.
Specifying the `-q' global option along with the `-r' command option is often useful, to suppress the warning messages when the RCS file does not contain the specified tag.
Warning: this is not the same as the overall `cvs -r' option, which you can specify to the left of a CVS command!
`-r' is available with the checkout, commit,
diff, history, export, rdiff,
rtag, and update commands.
-W
import,
and update.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This is the CVS interface to assorted administrative facilities. Some of them have questionable usefulness for CVS but exist for historical purposes. Some of the questionable options are likely to disappear in the future. This command does work recursively, so extreme care should be used.
On unix, if there is a group named cvsadmin,
only members of that group can run cvs admin
(except for the cvs admin -k command, which can
be run by anybody). This group should exist on the
server, or any system running the non-client/server
CVS. To disallow cvs admin for all users,
create a group with no users in it. On NT, the
cvsadmin feature does not exist and all users
can run cvs admin.
A.6.1 admin options
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Some of these options have questionable usefulness for CVS but exist for historical purposes. Some even make it impossible to use CVS until you undo the effect!
-Aoldfile
-alogins
-b[rev]
cvs admin -b: to revert to the vendor's
version when using vendor branches (see section 13.3 Reverting to the latest vendor release).
There can be no space between `-b' and its argument.
-cstring
-e[logins]
-I
-i
cvs add command
(see section 7.1 Adding files to a directory).
-ksubst
cvs update, cvs export, or cvs
checkout overrides this default.
-l[rev]
This can be used in conjunction with the `rcslock.pl' script in the `contrib' directory of the CVS source distribution to provide reserved checkouts (where only one user can be editing a given file at a time). See the comments in that file for details (and see the `README' file in that directory for disclaimers about the unsupported nature of contrib). According to comments in that file, locking must set to strict (which is the default).
-L
-mrev:msg
-Nname[:[rev]]
-nname[:[rev]]
-orange
Note that this command can be quite dangerous unless you know exactly what you are doing (for example see the warnings below about how the rev1:rev2 syntax is confusing).
If you are short on disc this option might help you. But think twice before using it--there is no way short of restoring the latest backup to undo this command! If you delete different revisions than you planned, either due to carelessness or (heaven forbid) a CVS bug, there is no opportunity to correct the error before the revisions are deleted. It probably would be a good idea to experiment on a copy of the repository first.
Specify range in one of the following ways:
rev1::rev2
::rev
rev::
rev
rev1:rev2
:rev
rev:
None of the revisions to be deleted may have branches or locks.
If any of the revisions to be deleted have symbolic
names, and one specifies one of the `::' syntaxes,
then CVS will give an error and not delete any
revisions. If you really want to delete both the
symbolic names and the revisions, first delete the
symbolic names with cvs tag -d, then run
cvs admin -o. If one specifies the
non-`::' syntaxes, then CVS will delete the
revisions but leave the symbolic names pointing to
nonexistent revisions. This behavior is preserved for
compatibility with previous versions of CVS, but
because it isn't very useful, in the future it may
change to be like the `::' case.
Due to the way CVS handles branches rev cannot be specified symbolically if it is a branch. See section 5.5 Magic branch numbers, for an explanation.
Make sure that no-one has checked out a copy of the revision you outdate. Strange things will happen if he starts to edit it and tries to check it back in. For this reason, this option is not a good way to take back a bogus commit; commit a new revision undoing the bogus change instead (see section 5.8 Merging differences between any two revisions).
-q
-sstate[:rev]
dead state for its own purposes; to
take a file to or from the dead state use
commands like cvs remove and cvs add, not
cvs admin -s.
-t[file]
If file is omitted, obtain the text from standard input, terminated by end-of-file or by a line containing `.' by itself. Prompt for the text if interaction is possible; see `-I'.
-t-string
-U
-u[rev]
commit
notification (see section 10.6.2 Telling CVS to notify you).
There can be no space between `-u' and its argument.
-Vn
-xsuffixes
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Create or update a working directory containing copies of the
source files specified by modules. You must execute
checkout before using most of the other CVS
commands, since most of them operate on your working
directory.
The modules are either symbolic names for some collection of source directories and files, or paths to directories or files in the repository. The symbolic names are defined in the `modules' file. See section C.1 The modules file.
Depending on the modules you specify, checkout may
recursively create directories and populate them with
the appropriate source files. You can then edit these
source files at any time (regardless of whether other
software developers are editing their own copies of the
sources); update them to include new changes applied by
others to the source repository; or commit your work as
a permanent change to the source repository.
Note that checkout is used to create
directories. The top-level directory created is always
added to the directory where checkout is
invoked, and usually has the same name as the specified
module. In the case of a module alias, the created
sub-directory may have a different name, but you can be
sure that it will be a sub-directory, and that
checkout will show the relative path leading to
each file as it is extracted into your private work
area (unless you specify the `-Q' global option).
The files created by checkout are created
read-write, unless the `-r' option to CVS
(see section A.4 Global options) is specified, the
CVSREAD environment variable is specified
(see section D. All environment variables which affect CVS), or a watch is in
effect for that file (see section 10.6 Mechanisms to track who is editing files).
Note that running checkout on a directory that was already
built by a prior checkout is also permitted.
This is similar to specifying the `-d' option
to the update command in the sense that new
directories that have been created in the repository
will appear in your work area.
However, checkout takes a module name whereas
update takes a directory name. Also
to use checkout this way it must be run from the
top level directory (where you originally ran
checkout from), so before you run
checkout to update an existing directory, don't
forget to change your directory to the top level
directory.
For the output produced by the checkout command
see A.16.2 update output.
A.7.1 checkout options A.7.2 checkout examples
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These standard options are supported by checkout
(see section A.5 Common command options, for a complete description of
them):
-D date
-f
-k kflag
status command can be viewed
to see the sticky options. See B. Quick reference to CVS commands, for
more information on the status command.
-l
-n
-P
-p
-R
-r tag
In addition to those, you can use these special command
options with checkout:
-A
-c
-d dir
There is an important exception, however. It is very convenient when checking out a single item to have the output appear in a directory that doesn't contain empty intermediate directories. In this case only, CVS tries to "shorten" pathnames to avoid those empty directories.
For example, given a module `foo' that contains the file `bar.c', the command `cvs co -d dir foo' will create directory `dir' and place `bar.c' inside. Similarly, given a module `bar' which has subdirectory `baz' wherein there is a file `quux.c', the command `cvs -d dir co bar/baz' will create directory `dir' and place `quux.c' inside.
Using the `-N' flag will defeat this behavior. Given the same module definitions above, `cvs co -N -d dir foo' will create directories `dir/foo' and place `bar.c' inside, while `cvs co -N -d dir bar/baz' will create directories `dir/bar/baz' and place `quux.c' inside.
-j tag
With one `-j' option, merge changes from the ancestor revision to the revision specified with the `-j' option, into the working directory. The ancestor revision is the common ancestor of the revision which the working directory is based on, and the revision specified in the `-j' option.
In addition, each -j option can contain an optional date specification which, when used with branches, can limit the chosen revision to one within a specific date. An optional date is specified by adding a colon (:) to the tag: `-jSymbolic_Tag:Date_Specifier'.
See section 5. Branching and merging.
-N
-s
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Get a copy of the module `tc':
$ cvs checkout tc |
Get a copy of the module `tc' as it looked one day ago:
$ cvs checkout -D yesterday tc |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Use commit when you want to incorporate changes
from your working source files into the source
repository.
If you don't specify particular files to commit, all of
the files in your working current directory are
examined. commit is careful to change in the
repository only those files that you have really
changed. By default (or if you explicitly specify the
`-R' option), files in subdirectories are also
examined and committed if they have changed; you can
use the `-l' option to limit commit to the
current directory only.
commit verifies that the selected files are up
to date with the current revisions in the source
repository; it will notify you, and exit without
committing, if any of the specified files must be made
current first with update (see section A.16 update--Bring work tree in sync with repository).
commit does not call the update command
for you, but rather leaves that for you to do when the
time is right.
When all is well, an editor is invoked to allow you to
enter a log message that will be written to one or more
logging programs (see section C.1 The modules file, and see section C.7 Loginfo)
and placed in the RCS file inside the
repository. This log message can be retrieved with the
log command; see A.13 log--Print out log information for files. You can specify the
log message on the command line with the `-m
message' option, and thus avoid the editor invocation,
or use the `-F file' option to specify
that the argument file contains the log message.
A.8.1 commit options A.8.2 commit examples
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These standard options are supported by commit
(see section A.5 Common command options, for a complete description of
them):
-l
-n
-R
-r revision
commit also supports these options:
-F file
-f
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
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Get a copy of the module `tc':
$ cvs checkout tc |
Get a copy of the module `tc' as it looked one day ago:
$ cvs checkout -D yesterday tc |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Use commit when you want to incorporate changes
from your working source files into the source
repository.
If you don't specify particular files to commit, all of
the files in your working current directory are
examined. commit is careful to change in the
repository only those files that you have really
changed. By default (or if you explicitly specify the
`-R' option), files in subdirectories are also
examined and committed if they have changed; you can
use the `-l' option to limit commit to the
current directory only.
commit verifies that the selected files are up
to date with the current revisions in the source
repository; it will notify you, and exit without
committing, if any of the specified files must be made
current first with update (see section A.16 update--Bring work tree in sync with repository).
commit does not call the update command
for you, but rather leaves that for you to do when the
time is right.
When all is well, an editor is invoked to allow you to
enter a log message that will be written to one or more
logging programs (see section C.1 The modules file, and see section C.7 Loginfo)
and placed in the RCS file inside the
repository. This log message can be retrieved with the
log command; see A.13 log--Print out log information for files. You can specify the
log message on the command line with the `-m
message' option, and thus avoid the editor invocation,
or use the `-F file' option to specify
that the argument file contains the log message.
A.8.1 commit options A.8.2 commit examples
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These standard options are supported by commit
(see section A.5 Common command options, for a complete description of
them):
-l
-n
-R
-r revision
commit also supports these options:
-F file
-f
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
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Get a copy of the module `tc':
$ cvs checkout tc |
Get a copy of the module `tc' as it looked one day ago:
$ cvs checkout -D yesterday tc |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Use commit when you want to incorporate changes
from your working source files into the source
repository.
If you don't specify particular files to commit, all of
the files in your working current directory are
examined. commit is careful to change in the
repository only those files that you have really
changed. By default (or if you explicitly specify the
`-R' option), files in subdirectories are also
examined and committed if they have changed; you can
use the `-l' option to limit commit to the
current directory only.
commit verifies that the selected files are up
to date with the current revisions in the source
repository; it will notify you, and exit without
committing, if any of the specified files must be made
current first with update (see section A.16 update--Bring work tree in sync with repository).
commit does not call the update command
for you, but rather leaves that for you to do when the
time is right.
When all is well, an editor is invoked to allow you to
enter a log message that will be written to one or more
logging programs (see section C.1 The modules file, and see section C.7 Loginfo)
and placed in the RCS file inside the
repository. This log message can be retrieved with the
log command; see A.13 log--Print out log information for files. You can specify the
log message on the command line with the `-m
message' option, and thus avoid the editor invocation,
or use the `-F file' option to specify
that the argument file contains the log message.
A.8.1 commit options A.8.2 commit examples
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These standard options are supported by commit
(see section A.5 Common command options, for a complete description of
them):
-l
-n
-R
-r revision
commit also supports these options:
-F file
-f
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
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Get a copy of the module `tc':
$ cvs checkout tc |
Get a copy of the module `tc' as it looked one day ago:
$ cvs checkout -D yesterday tc |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Use commit when you want to incorporate changes
from your working source files into the source
repository.
If you don't specify particular files to commit, all of
the files in your working current directory are
examined. commit is careful to change in the
repository only those files that you have really
changed. By default (or if you explicitly specify the
`-R' option), files in subdirectories are also
examined and committed if they have changed; you can
use the `-l' option to limit commit to the
current directory only.
commit verifies that the selected files are up
to date with the current revisions in the source
repository; it will notify you, and exit without
committing, if any of the specified files must be made
current first with update (see section A.16 update--Bring work tree in sync with repository).
commit does not call the update command
for you, but rather leaves that for you to do when the
time is right.
When all is well, an editor is invoked to allow you to
enter a log message that will be written to one or more
logging programs (see section C.1 The modules file, and see section C.7 Loginfo)
and placed in the RCS file inside the
repository. This log message can be retrieved with the
log command; see A.13 log--Print out log information for files. You can specify the
log message on the command line with the `-m
message' option, and thus avoid the editor invocation,
or use the `-F file' option to specify
that the argument file contains the log message.
A.8.1 commit options A.8.2 commit examples
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These standard options are supported by commit
(see section A.5 Common command options, for a complete description of
them):
-l
-n
-R
-r revision
commit also supports these options:
-F file
-f
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
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Get a copy of the module `tc':
$ cvs checkout tc |
Get a copy of the module `tc' as it looked one day ago:
$ cvs checkout -D yesterday tc |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Use commit when you want to incorporate changes
from your working source files into the source
repository.
If you don't specify particular files to commit, all of
the files in your working current directory are
examined. commit is careful to change in the
repository only those files that you have really
changed. By default (or if you explicitly specify the
`-R' option), files in subdirectories are also
examined and committed if they have changed; you can
use the `-l' option to limit commit to the
current directory only.
commit verifies that the selected files are up
to date with the current revisions in the source
repository; it will notify you, and exit without
committing, if any of the specified files must be made
current first with update (see section A.16 update--Bring work tree in sync with repository).
commit does not call the update command
for you, but rather leaves that for you to do when the
time is right.
When all is well, an editor is invoked to allow you to
enter a log message that will be written to one or more
logging programs (see section C.1 The modules file, and see section C.7 Loginfo)
and placed in the RCS file inside the
repository. This log message can be retrieved with the
log command; see A.13 log--Print out log information for files. You can specify the
log message on the command line with the `-m
message' option, and thus avoid the editor invocation,
or use the `-F file' option to specify
that the argument file contains the log message.
A.8.1 commit options A.8.2 commit examples
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These standard options are supported by commit
(see section A.5 Common command options, for a complete description of
them):
-l
-n
-R
-r revision
commit also supports these options:
-F file
-f
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
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Get a copy of the module `tc':
$ cvs checkout tc |
Get a copy of the module `tc' as it looked one day ago:
$ cvs checkout -D yesterday tc |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Use commit when you want to incorporate changes
from your working source files into the source
repository.
If you don't specify particular files to commit, all of
the files in your working current directory are
examined. commit is careful to change in the
repository only those files that you have really
changed. By default (or if you explicitly specify the
`-R' option), files in subdirectories are also
examined and committed if they have changed; you can
use the `-l' option to limit commit to the
current directory only.
commit verifies that the selected files are up
to date with the current revisions in the source
repository; it will notify you, and exit without
committing, if any of the specified files must be made
current first with update (see section A.16 update--Bring work tree in sync with repository).
commit does not call the update command
for you, but rather leaves that for you to do when the
time is right.
When all is well, an editor is invoked to allow you to
enter a log message that will be written to one or more
logging programs (see section C.1 The modules file, and see section C.7 Loginfo)
and placed in the RCS file inside the
repository. This log message can be retrieved with the
log command; see A.13 log--Print out log information for files. You can specify the
log message on the command line with the `-m
message' option, and thus avoid the editor invocation,
or use the `-F file' option to specify
that the argument file contains the log message.
A.8.1 commit options A.8.2 commit examples
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These standard options are supported by commit
(see section A.5 Common command options, for a complete description of
them):
-l
-n
-R
-r revision
commit also supports these options:
-F file
-f
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
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Get a copy of the module `tc':
$ cvs checkout tc |
Get a copy of the module `tc' as it looked one day ago:
$ cvs checkout -D yesterday tc |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Use commit when you want to incorporate changes
from your working source files into the source
repository.
If you don't specify particular files to commit, all of
the files in your working current directory are
examined. commit is careful to change in the
repository only those files that you have really
changed. By default (or if you explicitly specify the
`-R' option), files in subdirectories are also
examined and committed if they have changed; you can
use the `-l' option to limit commit to the
current directory only.
commit verifies that the selected files are up
to date with the current revisions in the source
repository; it will notify you, and exit without
committing, if any of the specified files must be made
current first with update (see section A.16 update--Bring work tree in sync with repository).
commit does not call the update command
for you, but rather leaves that for you to do when the
time is right.
When all is well, an editor is invoked to allow you to
enter a log message that will be written to one or more
logging programs (see section C.1 The modules file, and see section C.7 Loginfo)
and placed in the RCS file inside the
repository. This log message can be retrieved with the
log command; see A.13 log--Print out log information for files. You can specify the
log message on the command line with the `-m
message' option, and thus avoid the editor invocation,
or use the `-F file' option to specify
that the argument file contains the log message.
A.8.1 commit options A.8.2 commit examples
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These standard options are supported by commit
(see section A.5 Common command options, for a complete description of
them):
-l
-n
-R
-r revision
commit also supports these options:
-F file
-f
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
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Get a copy of the module `tc':
$ cvs checkout tc |
Get a copy of the module `tc' as it looked one day ago:
$ cvs checkout -D yesterday tc |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Use commit when you want to incorporate changes
from your working source files into the source
repository.
If you don't specify particular files to commit, all of
the files in your working current directory are
examined. commit is careful to change in the
repository only those files that you have really
changed. By default (or if you explicitly specify the
`-R' option), files in subdirectories are also
examined and committed if they have changed; you can
use the `-l' option to limit commit to the
current directory only.
commit verifies that the selected files are up
to date with the current revisions in the source
repository; it will notify you, and exit without
committing, if any of the specified files must be made
current first with update (see section A.16 update--Bring work tree in sync with repository).
commit does not call the update command
for you, but rather leaves that for you to do when the
time is right.
When all is well, an editor is invoked to allow you to
enter a log message that will be written to one or more
logging programs (see section C.1 The modules file, and see section C.7 Loginfo)
and placed in the RCS file inside the
repository. This log message can be retrieved with the
log command; see A.13 log--Print out log information for files. You can specify the
log message on the command line with the `-m
message' option, and thus avoid the editor invocation,
or use the `-F file' option to specify
that the argument file contains the log message.
A.8.1 commit options A.8.2 commit examples
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These standard options are supported by commit
(see section A.5 Common command options, for a complete description of
them):
-l
-n
-R
-r revision
commit also supports these options:
-F file
-f
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
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Get a copy of the module `tc':
$ cvs checkout tc |
Get a copy of the module `tc' as it looked one day ago:
$ cvs checkout -D yesterday tc |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Use commit when you want to incorporate changes
from your working source files into the source
repository.
If you don't specify particular files to commit, all of
the files in your working current directory are
examined. commit is careful to change in the
repository only those files that you have really
changed. By default (or if you explicitly specify the
`-R' option), files in subdirectories are also
examined and committed if they have changed; you can
use the `-l' option to limit commit to the
current directory only.
commit verifies that the selected files are up
to date with the current revisions in the source
repository; it will notify you, and exit without
committing, if any of the specified files must be made
current first with update (see section A.16 update--Bring work tree in sync with repository).
commit does not call the update command
for you, but rather leaves that for you to do when the
time is right.
When all is well, an editor is invoked to allow you to
enter a log message that will be written to one or more
logging programs (see section C.1 The modules file, and see section C.7 Loginfo)
and placed in the RCS file inside the
repository. This log message can be retrieved with the
log command; see A.13 log--Print out log information for files. You can specify the
log message on the command line with the `-m
message' option, and thus avoid the editor invocation,
or use the `-F file' option to specify
that the argument file contains the log message.
A.8.1 commit options A.8.2 commit examples
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These standard options are supported by commit
(see section A.5 Common command options, for a complete description of
them):
-l
-n
-R
-r revision
commit also supports these options:
-F file
-f
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
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Get a copy of the module `tc':
$ cvs checkout tc |
Get a copy of the module `tc' as it looked one day ago:
$ cvs checkout -D yesterday tc |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Use commit when you want to incorporate changes
from your working source files into the source
repository.
If you don't specify particular files to commit, all of
the files in your working current directory are
examined. commit is careful to change in the
repository only those files that you have really
changed. By default (or if you explicitly specify the
`-R' option), files in subdirectories are also
examined and committed if they have changed; you can
use the `-l' option to limit commit to the
current directory only.
commit verifies that the selected files are up
to date with the current revisions in the source
repository; it will notify you, and exit without
committing, if any of the specified files must be made
current first with update (see section A.16 update--Bring work tree in sync with repository).
commit does not call the update command
for you, but rather leaves that for you to do when the
time is right.
When all is well, an editor is invoked to allow you to
enter a log message that will be written to one or more
logging programs (see section C.1 The modules file, and see section C.7 Loginfo)
and placed in the RCS file inside the
repository. This log message can be retrieved with the
log command; see A.13 log--Print out log information for files. You can specify the
log message on the command line with the `-m
message' option, and thus avoid the editor invocation,
or use the `-F file' option to specify
that the argument file contains the log message.
A.8.1 commit options A.8.2 commit examples
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These standard options are supported by commit
(see section A.5 Common command options, for a complete description of
them):
-l
-n
-R
-r revision
commit also supports these options:
-F file
-f
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
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Get a copy of the module `tc':
$ cvs checkout tc |
Get a copy of the module `tc' as it looked one day ago:
$ cvs checkout -D yesterday tc |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Use commit when you want to incorporate changes
from your working source files into the source
repository.
If you don't specify particular files to commit, all of
the files in your working current directory are
examined. commit is careful to change in the
repository only those files that you have really
changed. By default (or if you explicitly specify the
`-R' option), files in subdirectories are also
examined and committed if they have changed; you can
use the `-l' option to limit commit to the
current directory only.
commit verifies that the selected files are up
to date with the current revisions in the source
repository; it will notify you, and exit without
committing, if any of