➜

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 doko
Recipients BreamoreBoy, LRN, Ray.Donnelly, WhiteTiger, alesko, amaury.forgeotdarc, davidfraser, doko, eric.araujo, georg.brandl, giampaolo.rodola, jhuntley, kalev, lkcl, rpetrov, rschoon.old, schmir, scott.tsai, tarek, tshepang
Date 2013-01-26.18:08:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1359223688.31.0.0114219471241.issue3871@psf.upfronthosting.co.za>
In-reply-to
Content 
> IMHO, updating these patches to track the latest Python is a pointless goal.

sorry, no. it's the *only* way to get these patches upstream. The mingw patches will never see the light of the 3.3 branch. So the best thing to do is to actively submit the patches for trunk.

If you do want to maintain your patches, then split your set of patches into those which are upstream (and then pack-ported), and which are not yet upstream.
History
Date User Action Args
2013-01-26 18:08:08dokosetrecipients: + doko, georg.brandl, lkcl, amaury.forgeotdarc, davidfraser, giampaolo.rodola, schmir, scott.tsai, tarek, eric.araujo, rpetrov, rschoon.old, WhiteTiger, BreamoreBoy, LRN, alesko, tshepang, kalev, Ray.Donnelly, jhuntley
2013-01-26 18:08:08dokosetmessageid: <1359223688.31.0.0114219471241.issue3871@psf.upfronthosting.co.za>
2013-01-26 18:08:08dokolinkissue3871 messages
2013-01-26 18:08:08dokocreate