Description:
------------
when bugs are reported to the bugs.php.net tracking system, often they are closed with a boilerplate message "this issue is fixed in CVS" without any information regarding the patch, what files were modified, the changeset id, etc.

for those of us who have to backport fixes to earlier releases, our work is made much more difficult because we have to go digging through CVS logs, the CVS news/rss feed, or the cvs web-based frontend with only a vague idea of the approximate time of the fix and files involved.  worse, if the fix introduces a regression that is later fixed in subsequent patches, we have no way of knowing apart from reading the latest CVS logs for the files in question.