The way we approach this in our team is to have a bug tracking database. When we fix a bug, we put a list of the files that changed in the database. Then we can query the database by bug number, file, or whatever. It's a little more work, but more flexible than trying to use CVS for this task.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeeva Sarma Sent: Wednesday, June 09, 2004 6:15 PM To: [EMAIL PROTECTED] Subject: Tags usage -- comments please Hi In our team, one developer wants to make tags for a few files; suppose he is working on 2 bugs, each requiring changes in 2 or 3 different set of files, he wants to tag each of those 2 or 3 files with the bug number, so that he can remember which files are modified for which bug. I think this is the wrong way to use tags, not the way they were intended to be used. I think log message is a better way to use in this case, we can later search the logs for the bug numbers. He doesn't agree. Any comments for/against this are greatly appreciated. Thanks, Jeeva __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
