I frequently use cvs rtag to tag the head (newest) revision on the trunk, so I
can capture the state of the repository code before making a major change. It
looks like:
% cvs rtag codeBeforeChange moduleName
% <make major change and commit>
% cvs rtag codeAfterChange moduleName
If you mess it up (of course, I never have that problem personally...), you can
easily refer to either the new or previous revisions in a convenient manner.
This also documents you change for others in the future, as not all mistakes are
immediately apparent. For example:
% <2 weeks passes>
% <problem arises>
% cvs diff -r codeBeforeChange -r codeAfterChange moduleName # identify
error
Of course, you must document the 2 tags "codeBeforeChange" and "codeAfterChange"
and what they represent so that you can use the tags a few weeks or years later.
Alan Thompson
