On Oct 28, 2008, at 6:22 PM, James Turnbull wrote:

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 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?
>
> The git log string is currently:
>
> git log --pretty=format:'%n%aD%n%an%ae%n%s'

As mentioned, I'd recommend at least having a space between name and  
email; I'd also probably put the commit message first, then person,  
then date (on three separate lines).

I still think we're going to need to either hand-customize the log to  
remove a lot of messages that just don't belong there (things that  
should be separate commits but not viewed as a separate change).   
Either that, or change our policy of having small, focused commits.

-- 
It's not to control, but to protect the citizens of Singapore. In our
society, you can state your views, but they have to be correct.
     -- Ernie Hai, co-ordinator of the Singapore Government
     Internet Project
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to