Well, it's not explicitly supported, but we use the comments field for that purpose. You can then write a query for that comment field, or more often look for the defect number and then look at the comments field for the list of files.
It's by a company called segue. It used to be called SilkRadar, but apparently they changed the name to SilkCentral Issue Manager. http://www.segue.com/products/test-management/silkcentral-issue-manager.asp -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, June 10, 2004 2:15 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Tags usage -- comments please Indeed. You can even have a *info script update the defect database with the files and version numbers. Your database maps files to defect numbers? Which product do you use, if it's not proprietary? --- Forwarded mail from [EMAIL PROTECTED] 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] 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. --- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs