What about "cvs -qn up -r bugfix16"?
Exactly my point - you have to define a label "bugfix16", and adhere to that naming convention. What if someone creates a label "BugFix18"? The system does not enforce any policy - you need the discipline to adhere to naming conventions, and the luck to avoid typos...
What's wrong with having a script to enforce this, e.g. "submit-bugfix 16"?
In my previous workplace we had a very very good locally evolved working procedure and command-line tools writen as Perl scripts wrapping Perforce and doing other stuff around it like updating the bugs database etc.
In my current workplace me and a co-worker from the previous workplace are trying to reach a similar state, currently on top of CVS.
Again, I agree that this is *possible* in CVS, but it depends on the
goodwill, self-discipline, and luck of all the programmers involved.
Programmer discipline is important in any case. You can make it easier by providing tools (e.g. scripts) which must be used in order to touch stuff in your CVS/bug-database.
--Amos
================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
