Éric Araujo <mer...@netwok.org> added the comment: To make commit review possible, I thought I’d make two patches for this: the first would be only markup fixes and minimal updates to match the reality of the code (i.e. convert setup.py examples to setup.cfg or pysetup, remove obsolete parts, etc.) and a second one with more rephrasing and reorganization (i.e. file deletions, moving chunks of docs, etc.). I’m not finished on the first patch and the diff already contains 1026 insertions and 921 deletions.
So, as potential commit reviewers, do you think I should - 1) go ahead with my initial plan of a huge boring commit and a more interesting commit - 2) just make one commit - 3) one commit per file (with boring markup changes + non-boring changes) ---------- nosy: +ezio.melotti, sandro.tosi _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12779> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
