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 zach.ware
Recipients brett.cannon, ezio.melotti, georg.brandl, lemburg, ncoghlan, orsenthil, pitrou, r.david.murray, sbt, terry.reedy, tshepang, zach.ware
Date 2014-03-20.21:04:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The `hg commit -l ...` tricks are just for those who tend to use exactly the same text for commit message and NEWS, and I only point them out simply because I don't know how many people are even aware of the -l option :).  If you want to use a NEWS entry as a base for a commit message without the two being exactly the same, it's also fairly easy to do ` | hg commit -l - && hg commit --amend` which will open the commit message in your usual commit message editor (at the cost of rolling back and re-doing the commit).

I also just thought of adding a 'who wrote it' question, and I like the idea of using it to manage Misc/ACKS.  I'm also intrigued by the suggestion of using Tkinter (when available), and the WhatsNew management.  But as you said, one thing at a time :)

First thing is, decide what we're actually going to do. obviously needs a fair bit of work before we can use it regularly, which I don't mind doing, but only if it will actually be used ;)
Date User Action Args
2014-03-20 21:04:47zach.waresetrecipients: + zach.ware, lemburg, brett.cannon, georg.brandl, terry.reedy, ncoghlan, orsenthil, pitrou, ezio.melotti, r.david.murray, tshepang, sbt
2014-03-20 21:04:47zach.waresetmessageid: <>
2014-03-20 21:04:47zach.warelinkissue18967 messages
2014-03-20 21:04:47zach.warecreate