Java Reference
In-Depth Information
your source. You should never need to mess with the files in the CVS directory;
see the Cederqvist reference in Section 8.6 for more information about
these files.
8.2.3
The typical use of CVS occurs after you've made some changes to your source
code. At some point, typically after the code compiles cleanly or after the
changes have been tested to some extent, you will want to commit your changes
to the CVS repository. When you commit one or more files, they become the
latest version, the version that others get when they checkout or update the
module. To say it another way, when you commit, you make those changes a
permanent part of the source repository, available to others.
You can commit a single file at a time, like this:
Normal Use
$ cvs commit Account.java
Or you can commit several files at a time, like this:
$ cvs commit Account.java User.java Xyz.java
Or you can commit all the changes from a certain point in the filesystem
hierarchy (e.g., the current directory) on down, like this:
$ cvs commit
(Specifying no files implies the current directory. You can also name a directory
explicitly.)
When you commit changes, CVS wants you to provide a bit of commen-
tary to explain what you've changed, to say something about this new version.
The comment can be supplied on the command line, with the -m option:
$ cvs commit -m "bug fix"
If you don't provide the -m parameter and its argument, CVS will invoke
your favorite editor (as specified in the environment variable CVSEDITOR or
VISUAL or else EDITOR , in that order of precedence). The default, on Linux
systems, is to invoke vi (see Figure 8.2). In the editor, you can type one or more
lines of text; when you exit, the commit will continue to completion.
Search WWH ::




Custom Search