<p dir="ltr"><br>
On May 25, 2013 9:18 PM, "Nick Coghlan" <<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>> wrote:<br>
><br>
> On Sun, May 26, 2013 at 9:41 AM, Brett Cannon <<a href="mailto:brett@python.org">brett@python.org</a>> wrote:<br>
> >> The NEWS update script could even use the revision history to decide<br>
> >> which order to add entries to the bulleted list.<br>
> ><br>
> > I think the annoyance with this approach is you will have to remember<br>
> > to add a file every time you do anything worthy of NEWS. Without<br>
> > something like ``hg newsworthy`` to take an optional issue # and then<br>
> > have you enter your NEWS entry and then use that to pre-populate the<br>
> > commit message, people will forget. Now granted adding the commit<br>
> > later is not a huge deal, but it is something that might happen if you<br>
> > forget to ``hg st`` before committing.<br>
><br>
> How is that any different from the status quo with people forgetting<br>
> an entry in NEWS? Just the extra step of needing to "hg add" the news<br>
> entry?</p>
<p dir="ltr">I didn't think there was a forgetfulness issue. I'm just trying to lower the overhead of doing a merge.</p>
<p dir="ltr">><br>
> Well, perhaps we can do this in two phases - resolve the persistent<br>
> problem of merge conflicts first, and then worry about the separate<br>
> push race problem later.</p>
<p dir="ltr">If we can ever agree on a solution. :)</p>
<p dir="ltr">-brett</p>
<p dir="ltr">><br>
> Cheers,<br>
> Nick.<br>
><br>
> --<br>
> Nick Coghlan | <a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a> | Brisbane, Australia<br>
</p>