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 pitrou
Recipients Arfrever, amaury.forgeotdarc, doko, eric.araujo, ezio.melotti, jwilk, lemburg, loewis, neologix, petri.lehtinen, pitrou, r.david.murray, rosslagerwall, vstinner
Date 2011-07-09.13:29:27
SpamBayes Score 0.000137344
Marked as misclassified No
Message-id <1310218112.3677.2.camel@localhost.localdomain>
In-reply-to <1310218025.74.0.175706858316.issue12326@psf.upfronthosting.co.za>
Content
> while this is sorted out, I propose to apply the following workaround
> not to introduce `linux3', at least for the branches:

It's too late, since existing versions won't have the patch and will
show "linux3" when the kernel gets upgraded.

I think we'd better bite the bullet and accept the "linux3" value.
History
Date User Action Args
2011-07-09 13:29:28pitrousetrecipients: + pitrou, lemburg, loewis, doko, amaury.forgeotdarc, vstinner, jwilk, ezio.melotti, eric.araujo, Arfrever, r.david.murray, neologix, rosslagerwall, petri.lehtinen
2011-07-09 13:29:28pitroulinkissue12326 messages
2011-07-09 13:29:27pitroucreate