Frank Wierzbicki added the comment: > 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16886> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
