Marc-Andre Lemburg <m...@egenix.com> added the comment: Sandro Tosi wrote: > > Sandro Tosi <sandro.t...@gmail.com> added the comment: > > On Tue, Apr 12, 2011 at 23:34, Marc-Andre Lemburg > <rep...@bugs.python.org> wrote: >> Sandro Tosi wrote: >>> >>> Sandro Tosi <sandro.t...@gmail.com> added the comment: >>> >>> In addition, is there a reason for the sorting of UTF-8 UTF-32 UTF-16 and >>> UTF-7 sections? why not alphabetically? >> >> No particular reason. Alphabetical order would be just as good. >> >> Note that such changes would have to be backported in order to >> keep the merge conflicts to a minimum. > > It applies cleanly on 3.2 (module some offsets), not as good on 3.1 > and 2.7: do you want me to prepare patches specifically for those 2 > brances?
I think you misunderstood: when reorganizing the contents of a file, it's better to apply the patch to all branches, rather than just the current, since otherwise future patches that do have to be merged to all branches would cause lots of merge conflicts. >>> Also, several parts of the doc would need paragraph re-indentation (not >>> done in this patch due to clarity). >> >> Not sure what you mean here. > > sorry, I meant wrap at 80th column (or so) :) Ah, ok. That's the same category of change as the reorg above (due to diff working line-based and not word based). Such changes are fine, but should only be applied occasionally and then preferably as one big commit to minimize disruption. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11840> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
