Committing Changes
Once you’ve checked out
project files into a sandbox, you can edit those files with your
preferred editor. Changes are not synchronized with the repository
until you run the cvs commit
command.
This command is best run from the root directory of your sandbox, and
it must be run from within the sandbox.
Commit to the repository frequently. Rules of thumb for when to commit include “every time the code compiles cleanly” and “every day before lunch and before you leave.”
Tip
In programming projects with several developers, try to avoid committing code that doesn’t compile.
When you commit, CVS examines each directory and subdirectory below
the current working directory. It searches for files that it is
tracking that have changed, and commits all changes to the
repository. See Example 2-12 for an example of
committing files. Remember, the repository path is stored in the
sandbox, so you don’t need to specify the path
explicitly in your cvs commit
command.
Example 2-12. Committing files
$cd ~/cvs/example
$cvs commit
cvs commit: Examining .
If your repository is not on the local machine and your repository server doesn’t have your SSH public key, CVS will ask for a password for the remote machine. If the server has the public key, your SSH client can use the private key to authenticate you.
If any files have been changed, CVS opens an
editor to allow you to record a change message. By default, the editor
is vi,
just as when importing a project. Chapter 3 gives instructions ...
Get Essential CVS now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.