Use the commit command to commit your local changes into the repository.
Click the Show Changes button to open the Change Report window for the selected files (see Change Report (Pro Only)).
Select Recurse into subdirectories when committing directories, to tell SmartCVS not only to commit the files in the selected directory, but those in subdirectories, too.
In Log Message you can enter a describing message about what you have done. To specify a clear message (e.g. 'fixed null-pointer exception') is a good idea to better track your changes. The messages for revisions that have already been committed can be viewed with Query|Show Transactions or Query|Log. Press <Ctrl>+<Space> to complete file names.
Note |
If there exists a Template file in the CVS subdirectory of the selected directory, the content of this file is read into the Log Message input field. To set up such a template file, consult the documentation of the CVSROOT/rcsinfo file in the repository. |
Select Force commit even if there are no changes to create a new revision of the file in the repository, even if the file hasn't changed.
Select Don't run the module program on the CVS-server, if you do not want the CVS-server to run a special command after your commit, e.g. for email notification about the change.
Select Refresh Remote State, when SmartCVS should refresh the Remote State after the commit. Select Refresh Editors (which only is enabled, if the Editors table column is visible), when the editors information should be refreshed after the commit.
If you want to add a tag to the committed file revisions, select the similar named checkbox and enter the commit tag.
Tip |
In general, it is often advisable to commit files as soon as possible. This reduces the risk of conflicts (changes made by co-workers at the same pieces of code) significantly. Of course it is also adviced to commit only changes, that compile, especially in the whole project. |