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 martin.panter
Recipients ezio.melotti, maciej.szulik, martin.panter, willingc
Date 2016-01-11.23:17:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452554230.3.0.0508834376526.issue23942@psf.upfronthosting.co.za>
In-reply-to
Content
I guess if people wonder about this, you could at least say the naming doesn’t matter very much for the review system.

If I am generating my own patches, I try to name them with one or two concise words describing the particular solution, and then insert “.v2”, “.v3” etc for the revised patches. If I just gave them an issue number, it would get lost my Mercurial patch queue among a sea of other numbers. If I did not add the “.v2” revision number, people would have to refer to the patches by upload date rather than name or version.
History
Date User Action Args
2016-01-11 23:17:10martin.pantersetrecipients: + martin.panter, ezio.melotti, maciej.szulik, willingc
2016-01-11 23:17:10martin.pantersetmessageid: <1452554230.3.0.0508834376526.issue23942@psf.upfronthosting.co.za>
2016-01-11 23:17:10martin.panterlinkissue23942 messages
2016-01-11 23:17:10martin.pantercreate