➜

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 r.david.murray
Recipients Arfrever, Duke.Dougal, Illirgway, barry, jesstess, lpolzer, maciej.szulik, python-dev, r.david.murray, richard, serhiy.storchaka, sreepriya, vstinner, zvyn
Date 2016-05-16.19:21:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1463426519.98.0.300573754388.issue27033@psf.upfronthosting.co.za>
In-reply-to
Content 
No problem.  I use 'commit review' as an indication that a committer should do a final review...before that, triage or general community people can be doing the reviews, then triage can move it to commit review to request the final review before commit.  What this means in practical terms is that if I do a search for 'email' issues in 'commit review' stage, I find all the issues I should be reviewing.

I'll try to do the review soon.
History
Date User Action Args
2016-05-16 19:22:00r.david.murraysetrecipients: + r.david.murray, barry, richard, vstinner, Arfrever, jesstess, python-dev, serhiy.storchaka, maciej.szulik, lpolzer, Illirgway, Duke.Dougal, zvyn, sreepriya
2016-05-16 19:21:59r.david.murraysetmessageid: <1463426519.98.0.300573754388.issue27033@psf.upfronthosting.co.za>
2016-05-16 19:21:59r.david.murraylinkissue27033 messages
2016-05-16 19:21:59r.david.murraycreate