James Turnbull wrote: > I am just adding a rake task to do the new CHANGELOG creation. I'd > like some input on the format. I've basically done: > > Tue, 28 Oct 2008 14:12:36 +0100 > Brice [EMAIL PROTECTED] > Fix #1682 - ASTArray should flatten product of evaluation of its children > > Tue, 28 Oct 2008 17:13:31 -0500 > Luke [EMAIL PROTECTED] > Fixing #1667 - regex automatic value documentation is now readable. > > Tue, 28 Oct 2008 15:57:03 +1100 > James [EMAIL PROTECTED] > Fixed #1692 - k5login fails to set mode when file is created > > But it's highly customisable. What else would people expect/like? > Hashes? The full commit?
If completely changing the CHANGELOG format is an option, what about just using "git log" output as is? That contains plenty of useful information and gives anyone reading the ability to dig deeper since it contains the commit sha1. > The git log string is currently: > > git log --pretty=format:'%n%aD%n%an%ae%n%s' You'd want to add a space after the author name and some brackets around the email address, to avoid output like: Luke [EMAIL PROTECTED] So, just tweaking your format options: git log --pretty=format:'%n%aD%n%an <%ae>%n%s' BTW, is it possible to run the tarball creation outside of reductivelabs? The DevelopmentLifecycle page on the wiki leads me to believe the answer is no, but if I am mistaken, I'd be happy to help test the Rakefile changes. -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The world keeps ending but new people too dumb to know it keep showing up as if the fun's just started.
pgpSlotfEX2U5.pgp
Description: PGP signature
