Java™ Application Development on Linux - Dator

8.2 Source Control: Whys and Hows205Note: do not put a space between the -w, -r, or -d and its parameter or CVSwill think that the parameter is the name of a source module, and you will seea message like this:$ cvs log -r 1.2:1.4 Account.javacvs log: nothing known about 1.2:1.4...which will be followed by output about the Account.java module that CVSdoes know about.For more variations on the logging output, type:$ cvs log --help8.2.7 cvs statusWhile the cvs log command will tell you about the history of all revisions ofa file, you sometimes need to know the status of the current file in your sandbox:Which revision is it? From where did it come? And, most importantly, isit part of the head or part of a branch?Those questions can be answered with the cvs status command. Itsoutput will show the revision number of the file in your sandbox and any“sticky” tags. But to understand what that means, we need to talk about tagsfirst.8.2.8 cvs tagWe began this chapter asking: “Can you find or create a set of sources thatmatches exactly what your customer is running? Can you then provide a modifiedversion that contains only the fix necessary and no other changes?” Partof the answers to these questions will depend on your use of the cvs tagcommand. With it, you can set down a label across all your source to mark aparticular milestone, so that later you can recall that version of the source.For example,$ cvs tag Rel_2_4will put a tag (that is, a label) called Rel_2_4 on the head revision of all sourcefiles from the directory where this command was executed on down through