> > CVS's support for bug > > tracking is poor to nonexistent and many people have commented on > > it and requested better support. > > That's because CVS is not a bug tracking tool. It's an archive > system. Only an archive system. If you want to do more than just > archiving, you must find tools that do those other things and/or > integrate them yourself.
Accepting the harsh truth of Mike's statement, may I ask the group whether anyone has any particular recommendations or useful script to share which can usefully link Bugzilla-stored issues with CVS revisions? I'm thinking along the lines of bug ID's which may be entered into log comments, etc. I can and will write such a thing if need be, but I'm wondering what wheels already exist that people can personally endorse. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
