I agree. In my previous company build process provided report in a format: bugID/changeID bug description developer, who fixed developer's CVS comments associated with the fix list of files modified for the bug
This was a very effective way to communicate source changes, because it provided the context for the change. It was all an in-house development. This information is extremely valuable for QA, who can focus their effort based on the list of modified files. Eugene. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >--- Forwarded mail from [EMAIL PROTECTED] >Let me turn your question around: how often have you had to determine >exactly which files have been affected by a specific bug fix? (This is an >open question to anyone reading this message). I cannot recall ever needing >this information. It happens often enough when you want to port a specific bug fix to a new branch. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
