:local:/home/myusername/cvsroot

or just /home/myusername/cvsroot since CVS assumes local mode by

default. The other two options in the dialog allow you to enable or

disable "auto commit/update changes" made to your projects when you

open or close them.

Now having at least one repository specified in your configuration, you

can easily put your project under version control. Press F10 to

activate the menu and select "CVS->Import into CVS" item. You will

be asked to select a repository to import a project into. Then wait a while

as the project is imported.

After importing the files of your project into the CVS repository you can

access all the CVS functionality. You can watch and then commit and/or

update changes, see the history and check out old releases and

modifications.

After you select this item in the "Debug" menu, Motor runs CVS to

check for modifications in your source and compares your local version

with the repository. Then the report is displayed saying what files were

changed. In this dialog you can "Update" (synchronize your local copy

with the repository getting all the changes and applying them to your

local source), "Commit" (send your local changes in the repository)

and "Tag a release".

This option is useful when you think the source is ok (stable?) and

you want to put a milestone to be able to roll back in case any bugs appear

because of further modifications. It can be run from

several places: from the menu, from the check in/out dialog and from the

distribution generation dialog. After you select this item, you are

asked for a release name. Note, it must start with a letter. Once a

release is tagged, it appears on the release history every time you

invoke it.

Since the changes and comments are held in the repository, there must

be a way to view the history. There are two histories. File history

displays a chronological sequence of modifications and comments for