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 fwierzbicki
Recipients eric.araujo, ezio.melotti, fwierzbicki, r.david.murray, serhiy.storchaka
Date 2013-01-11.22:46:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357944367.77.0.849350893503.issue16886@psf.upfronthosting.co.za>
In-reply-to
Content
> Well, we generally prefer to go through the review process always, except for relatively small commits (which some of yours may be).

Good to know, in that case I'll plan to go through the review process always.

> 2.7 is separate from 3.x.  So to commit to all four branches you commit to 3.2, merge to 3.3, merge to default, and the graft to 2.7.  (Myself, I'm still using patch to do the 2.7 updates, I haven't tried graft yet.)

When you say "use patch" to do the 2.7 update - do you mean a manual patch? I'm not ready to look into graft and would prefer to just do the regular thing for now.

> (In theory this should all be in the devguide...)
I'll definitely be reading the devguide as I prepare to push my changes.
History
Date User Action Args
2013-01-11 22:46:07fwierzbickisetrecipients: + fwierzbicki, ezio.melotti, eric.araujo, r.david.murray, serhiy.storchaka
2013-01-11 22:46:07fwierzbickisetmessageid: <1357944367.77.0.849350893503.issue16886@psf.upfronthosting.co.za>
2013-01-11 22:46:07fwierzbickilinkissue16886 messages
2013-01-11 22:46:07fwierzbickicreate