Cvs remove sticky tag without updating
Tagging is a way of marking a group of file revisions as belonging together.You can't use the revision numbers for this purpose, because revision 2.3 of one file might belong with revision 2.17 of another.The syntax for the cvs tag command is: cvs tag determines which files and revisions to mark based on your sandbox, but it marks them based on the revision that was most recently synchronized with the repository.If changes have occured in the sandbox since the files were last synchronized with the repository, those changes will not be reflected in the tagged revisions.Tag names must start with a letter and can contain alphanumeric characters, hyphens (-), and underscores (_). You tag files with the cvs tag and cvs rtag commands, explained in Section 4.1.1 and Section 4.1.2 of this chapter. Tag names should immediately tell you something about the revisions they tag and, if they tag across several files, why those revisions belong together.
The CVS numbers are intended to be internal tools for CVS's use and can be difficult for humans to relate to stages of the project. CVS uses the BASE tag name for the revision that was last synchronized with the repository.Remembering the significance of a text string is much easier than remembering a version number.Tags are often used to record the version number used by the developers, rather than the CVS revision number, which is used primarily as a CVS internal designation.If your coworker commits twice, the BASE revision for your sandbox is still 1.23, because you haven't synchronized with the changes in the repository.The HEAD revision is now 1.25, because your coworker's two commits were given revision numbers 1.24 and 1.25.