Éric Araujo <mer...@netwok.org> added the comment: The whole file is ordered with newest on top (newest Python version), so I guess it’s implicit for all committers that sections are also ordered with newest on top. It does not actually matter; the contents of one “what’s new in Python W.XyZ” are not ordered.
A nice trick to make Mercurial’s automatic file merge work is to put your entry after the first or the first two entries, so that if you commit, then pull new changesets and merge, the merge will success automatically. ---------- nosy: +eric.araujo _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15260> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
