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 ezio.melotti
Recipients chris.jerdonek, eric.araujo, ezio.melotti, ncoghlan, pitrou, sandro.tosi, terry.reedy, tshepang
Date 2013-02-01.03:38:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1359689928.1.0.652665116641.issue14468@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not sure what's the point though.  The repo on bitbucket provides an easy way to review individual changes, and pushing everything at once prevents history pollution (assuming you consider 8 related changesets as pollution).  That's similar to the process we follow for feature branches, except that this is trivial enough that I didn't create a branch.
History
Date User Action Args
2013-02-01 03:38:48ezio.melottisetrecipients: + ezio.melotti, terry.reedy, ncoghlan, pitrou, eric.araujo, sandro.tosi, chris.jerdonek, tshepang
2013-02-01 03:38:48ezio.melottisetmessageid: <1359689928.1.0.652665116641.issue14468@psf.upfronthosting.co.za>
2013-02-01 03:38:48ezio.melottilinkissue14468 messages
2013-02-01 03:38:47ezio.melotticreate