Java™ Application Development on Linux - Dator

8.2 Source Control: Whys and Hows203In such a case, the programmer must decide which changes to keep, orhow to combine them. After editing the file and removing the dividing lines(i.e., ), recompiling and probably a bit of testing,too, the programmer can now do a cvs commit to incorporate his changes inthe repository.8.2.6 LogWith each cvs commit you are prompted for a comment, to describe thechanges that you are committing. What happens to these comments? How canyou see them again? Use the cvs log command to show the history of a file’srevisions and associated comments.See Example 8.2 for an example of the cvs output command.Looking down the output of cvs log, you can see• The complete filename—in the repository—of the file whose log we’rechecking out.• The local filename in your sandbox.• Which revision is the “head,” that is, the front-most or default revision.• Which branch, if any.• What kind of locking mechanism CVS uses. There are some choices, butmost users of CVS leave this as is.• The access limitations. CVS can limit who can modify files (see ourreference list if you need to use this).• A list of all the tags (symbolic names) for this module and to whichrevision each refers.• What kind of keyword substitution happens. For binary files this wouldbe kb.• The count of revisions for this file.Then comes a description of each of the revisions, showing• The revision number.• Some stats on the change including the user ID of the user who committedthe change.• How many lines were added and deleted compared to the previous revision.