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 maciej.szulik
Recipients ezio.melotti, maciej.szulik, willingc
Date 2015-04-13.23:02:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1428966137.48.0.790822523429.issue23942@psf.upfronthosting.co.za>
In-reply-to
Content
During the lifecycle of a bug you do:
1. submit a patch
2. get a review with some comments
3. re-submit the patch

Talking to R. David Murray I got info there's no convention on naming those, I think it will be valuable to have some information in the devguide about that. 

Apparently you can either (when just fixing the patch) to stick with exactly the same name or add increasing suffix, eg. mypatch-1, mypatch-2, etc.).  Otherwise you can change the name, but the review system will be able to pick up the right patch, so you should not worry about that.
History
Date User Action Args
2015-04-13 23:02:17maciej.szuliksetrecipients: + maciej.szulik, ezio.melotti, willingc
2015-04-13 23:02:17maciej.szuliksetmessageid: <1428966137.48.0.790822523429.issue23942@psf.upfronthosting.co.za>
2015-04-13 23:02:17maciej.szuliklinkissue23942 messages
2015-04-13 23:02:17maciej.szulikcreate