Know What You Have: CVS - Java Application Development on Linux - page 197

mydir

prev coolj misc

FetchURL.java Sprit.java Tux.java

Figure 8.1 A sample directory structure prior to import

This will create a module named coolj in the repository, whose contents
are all the directories and subdirectories that you see there. But you had to be
in the coolj directory, which may seem counter-intuitive.
Now go to some other directory, one that is not part of the coolj part of
the tree, and check out a copy of the source. For example:

$ cd
$ mkdir devsrc
$ cd devsrc
$ cvs checkout coolj

NOTE
It is important to check out the source after you've done the import, and before
you make any changes, because the part of the filesystem that you imported
remains untouched. It has no CVS knowledge, so you can't commit changes
from that directory, unless you somehow make it CVS-aware. Since these files
are your originals, until you've verified that the cvs import has gone as
planned, it's best not to disturb those files. Create a new directory and check
out the module there.

What do you see after the checkout? There should be a single directory,
coolj , in the directory where you did the checkout (since it was empty when
you started). That directory contains a copy of all the files that you checked in,
along with a directory named CVS inside that directory and every subdirectory.
The CVS directories contain administrative files that help CVS keep track of
things for you, which means no CVS tracking information needs to be kept in