"Paul Gelderblom \(ptok\)" writes: > > This is a multi-part message in MIME format.
Please do not send MIME and/or HTML encrypted messages to the list. Plain text only, PLEASE! > However, we have found out that sometimes commit on these sticky tags > succeed, because CVS somewhere in the process _converts_ the sticky > normal tag into > a branch! This happens when there are empty directories in the > tree on which cvs update -r TAG has been done. The problem is that tags do not have an independent existance -- they only exist inside RCS files. Thus, a tag can be a branch tag in one file and a non-branch tag in another. The rule CVS uses is that if the tag is a non-branch tag in any file in the directory, then the tag is marked as a non-branch tag in the CVS/Tag file; otherwise, it is marked as a branch tag, which naturally results in a branch tag in an empty directory. Just one more reason why you should always use -P on checkout and update and not try to store empty directories in CVS. > I guess that N means Tag and T means Branch(!), but could not > find documentation on the Tag file format in the CVS dox. Did you try looking in the index? <http://www.cvshome.org/docs/manual/cvs-1.11.7/cvs_2.html#IDX45> -Larry Jones I've never seen a sled catch fire before. -- Hobbes _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs