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 meador.inge
Recipients alex, ezio.melotti, mark.dickinson, meador.inge, terry.reedy
Date 2011-09-24.02:20:57
SpamBayes Score 1.6211317e-06
Marked as misclassified No
Message-id <1316830858.86.0.819835023986.issue13012@psf.upfronthosting.co.za>
In-reply-to
Content
> Doing two separate commits is probably better.

Out of curiosity, what is typically the convention on that?  The 
devguide seems to suggest one changeset per issue:

"""
Just please make sure that you generate a single, condensed patch rather than a series of several changesets.
"""

I think for this case two patches is better.  In general, I am OK with
the git-style series and hg-style patchbombs, but the devguide seems
to say otherwise.  Hmmm, that makes me wonder if we can patchbomb the
tracker :-)
History
Date User Action Args
2011-09-24 02:20:58meador.ingesetrecipients: + meador.inge, terry.reedy, mark.dickinson, ezio.melotti, alex
2011-09-24 02:20:58meador.ingesetmessageid: <1316830858.86.0.819835023986.issue13012@psf.upfronthosting.co.za>
2011-09-24 02:20:58meador.ingelinkissue13012 messages
2011-09-24 02:20:57meador.ingecreate