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 jgehrcke
Recipients asvetlov, brandon-rhodes, christian.heimes, dstufft, giampaolo.rodola, jcea, jgehrcke, kristjan.jonsson, martius, njs, orsenthil, pitrou
Date 2017-11-28.17:48:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Hello! I would very much appreciate if we can find a way for us to get another review for the last patch.

I did most of the work in August 2016 and got a review from Senthil and Christian which I processed. When I got back to the patch for converting it to the GitHub workflow about a year later I realized that the details faded from my mind. 4 months later, after re-digging into the details, I went into the patch again and resolved the merge conflicts that accumulated over time. Antoine kindly left another round of comments which I replied to.

Now, 2 months after that last effort I'd like to not forget about the details again, but instead be able to respond to review feedback while still being on top of the matter. So, any kind and level of feedback would be greatly appreciated.

Thank you!
Date User Action Args
2017-11-28 17:48:57jgehrckesetrecipients: + jgehrcke, jcea, orsenthil, pitrou, kristjan.jonsson, giampaolo.rodola, christian.heimes, njs, asvetlov, brandon-rhodes, dstufft, martius
2017-11-28 17:48:56jgehrckesetmessageid: <>
2017-11-28 17:48:56jgehrckelinkissue16487 messages
2017-11-28 17:48:56jgehrckecreate