➜

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 eric.araujo
Recipients chris.jerdonek, eric.araujo, ezio.melotti
Date 2012-07-06.16:30:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1341592208.98.0.818155389204.issue15260@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2012-07-06 16:30:09eric.araujosetrecipients: + eric.araujo, ezio.melotti, chris.jerdonek
2012-07-06 16:30:08eric.araujosetmessageid: <1341592208.98.0.818155389204.issue15260@psf.upfronthosting.co.za>
2012-07-06 16:30:08eric.araujolinkissue15260 messages
2012-07-06 16:30:08eric.araujocreate