Derek Robert Price writes: > Corrected, reworded, added, and committed.
Thanks! > Please include ChangeLog entries with future patch submissions, as per > the instructions in the HACKING file in the toplevel of the CVS source > distribution. I'll keep this in mind. Just trying to make it a little easier to use; we've found a fair bit of resistance to doing anything via the commitinfo mechanism since there's not a lot of detail in the docs and consequently little confidence that it's been as thoroughly tested as the basic internal operations. It would also be very helpful if more information was available to scripts run via commitinfo, such as previous/new revision numbers, the branch being affected, etc. The branch information would be especially helpful since it can reasonably play a part in authorization checks for commits, which is part of the stated intention of commitinfo scripts. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation _______________________________________________ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
