Add some sanity checking to make sure that the user is tagging the
highest revision on the branch (or trunk) of the magic .template file, since doing otherwise would seem to indicate an inconsistency in what the user is doing. Why? Templates are modified via a tag operation of the .template file, but splitting off can only be done via a branch operation. Subsequent mods after a branch have to happen along a straight line. Also allow for tag moving to initiate a template modify since the above implied error can be corrected by doing a cvs update, and then a retag with the -F option to move the tag.
Showing with 104 additions and 15 deletions