Thanks everyone for their responses but I need some additional
clarification.  

1)  I checked out all my files prior to the vendors putting the sticky tags
on.  So why are the sticky tags effecting me?  Is it because commit verifies
that the selected files are up to date with the current revision in the
repository?  It doesn't make sense that it would be looking at the branch
tags ... doesn't it compare with the trunk from where I originally checked
out? 

2)  removing the sticky tags (cvs update -A), does not effect the sticky
tags in the repository just in my local copy?

3)  Do I need to worry about any conflicts because there is a tag and a
sticky tag with identical names?  It must not have given the vendors any
warning but it just doesn't seem right to have a tag for release with the
same name as a branch tag.

Jeanie

_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Reply via email to