Message 216931 - Python tracker

Message216931

Author	terry.reedy
Recipients	brett.cannon, ezio.melotti, georg.brandl, lemburg, ncoghlan, pitrou, r.david.murray, sbt, terry.reedy, tshepang, zach.ware
Date	2014-04-21.00:34:29
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<53546763.5030408@udel.edu>
In-reply-to	<1398038381.28.0.0719956846162.issue18967@psf.upfronthosting.co.za>

Content
On 4/20/2014 7:59 PM, Antoine Pitrou wrote: > > Antoine Pitrou added the comment: > >> This is already not a rule because the devguide mentions inserting new >> items at random positions to avoid conflicts due to another commit. > > Really? > > """New NEWS entries are customarily added at or near the top of their respective sections, so that entries within a section appear in approximate order from newest to oldest. However, this is customary and not a requirement.""" Random is too loose for what was actually committed and I will correct it. Further down in the same section: "A nice trick to make Mercurial’s automatic file merge work more smoothly is to put a new entry after the first or first two entries rather than at the very top. This way if you commit, pull new changesets and merge, the merge will succeed automatically." >> In any case, the News entries are not necessarily time ordered now. > > IME, they mostly are. It's true it's not a requirement.

Content

On 4/20/2014 7:59 PM, Antoine Pitrou wrote:
>
> Antoine Pitrou added the comment:
>
>> This is already not a rule because the devguide mentions inserting new
>> items at random positions to avoid conflicts due to another commit.
>
> Really?
>
> """New NEWS entries are customarily added at or near the top of their respective sections, so that entries within a section appear in approximate order from newest to oldest. However, this is customary and not a requirement."""

Random is too loose for what was actually committed and I will correct 
it. Further down in the same section: "A nice trick to make Mercurial’s 
automatic file merge work more smoothly is to put a new entry after the 
first or first two entries rather than at the very top. This way if you 
commit, pull new changesets and merge, the merge will succeed 
automatically."

>> In any case, the News entries are not necessarily time ordered now.
>
> IME, they mostly are. It's true it's not a requirement.

History
Date	User	Action	Args
2014-04-21 00:34:30	terry.reedy	set	recipients: + terry.reedy, lemburg, brett.cannon, georg.brandl, ncoghlan, pitrou, ezio.melotti, r.david.murray, tshepang, sbt, zach.ware
2014-04-21 00:34:30	terry.reedy	link	issue18967 messages
2014-04-21 00:34:29	terry.reedy	create