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 r.david.murray
Recipients eric.araujo, ezio.melotti, fwierzbicki, r.david.murray, serhiy.storchaka
Date 2013-01-11.20:12:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357935121.02.0.744669223596.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).

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.)  Before you push, you should have 2.7 and default as active branches (hg branches) but no others.  And if push tells you you are trying to create remote heads, that generally means someone else pushed since your last pull, and you will need to merge their heads with yours before you can push.

(In theory this should all be in the devguide...)
History
Date User Action Args
2013-01-11 20:12:01r.david.murraysetrecipients: + r.david.murray, fwierzbicki, ezio.melotti, eric.araujo, serhiy.storchaka
2013-01-11 20:12:01r.david.murraysetmessageid: <1357935121.02.0.744669223596.issue16886@psf.upfronthosting.co.za>
2013-01-11 20:12:00r.david.murraylinkissue16886 messages
2013-01-11 20:12:00r.david.murraycreate