This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients alex, ezio.melotti, mark.dickinson, meador.inge, terry.reedy
Date 2011-09-24.02:36:44
SpamBayes Score 1.53639e-06
Marked as misclassified No
Message-id <1316831805.14.0.86000360703.issue13012@psf.upfronthosting.co.za>
In-reply-to
Content
One changeset per issue is a general goal. So is the ability to review patches. Sometime people forget to add a News or Acks entry and have to followup with an addendum. (Mark's patch still lack that, for instance.) Sometimes a patch is so large that a reviewer asks or requires splitting. In this case, each patch is large enough and touches enough files (up to 10 I think) that two is plausible. What would not be appreciated by either a reviewer or commit-list recipients would be one patch file per patched file. That would be a patch bomb indeed ;-)
History
Date User Action Args
2011-09-24 02:36:45terry.reedysetrecipients: + terry.reedy, mark.dickinson, ezio.melotti, alex, meador.inge
2011-09-24 02:36:45terry.reedysetmessageid: <1316831805.14.0.86000360703.issue13012@psf.upfronthosting.co.za>
2011-09-24 02:36:44terry.reedylinkissue13012 messages
2011-09-24 02:36:44terry.reedycreate