Java™ Application Development on Linux - Dator

8.2 Source Control: Whys and Hows197mydirprev coolj miscFetchURL.java Sprit.java Tux.javaFigure 8.1 A sample directory structure prior to importThis will create a module named coolj in the repository, whose contentsare all the directories and subdirectories that you see there. But you had to bein the coolj directory, which may seem counter-intuitive.Now go to some other directory, one that is not part of the coolj part ofthe tree, and check out a copy of the source. For example:$ cd$ mkdir devsrc$ cd devsrc$ cvs checkout cooljNOTEIt is important to check out the source after you’ve done the import, and beforeyou make any changes, because the part of the filesystem that you importedremains untouched. It has no CVS knowledge, so you can’t commit changesfrom that directory, unless you somehow make it CVS-aware. Since these filesare your originals, until you’ve verified that the cvs import has gone asplanned, it’s best not to disturb those files. Create a new directory and checkout 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 whenyou 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 ofthings for you, which means no CVS tracking information needs to be kept in