It would be helpful if folks could format their git commit message with a one line summary (80 char or less), followed by a blank line then a more lengthy detailed description (if necessary).
For example,
lot's of code cleanup, removed dead code.
Removed unused imports Removed a bunch of unused code
etc.
This simple change will help make the automated changelogs easier to consume since I don't have to clean them up.
Thanks jesus
Can we break on the first sentence, not line So..
I did cool shite. Really, this is cool.
that way I can use commit -m
-- bk
On 04/23/2010 09:24 AM, Jesus Rodriguez wrote:
It would be helpful if folks could format their git commit message with a one line summary (80 char or less), followed by a blank line then a more lengthy detailed description (if necessary).
For example,
lot's of code cleanup, removed dead code. Removed unused imports Removed a bunch of unused code
etc.
This simple change will help make the automated changelogs easier to consume since I don't have to clean them up.
Thanks jesus
On Fri, Apr 23, 2010 at 09:29:21AM -0400, Bryan Kearney wrote:
Can we break on the first sentence, not line So..
I did cool shite. Really, this is cool.
that way I can use commit -m
It's not a requirement :) I review all of the messages before committing the changelog and clean them up. I guess I could make tito smart to break on the first sentence.
jesus
On 04/23/2010 09:28 AM, Jesus Rodriguez wrote:
On Fri, Apr 23, 2010 at 09:29:21AM -0400, Bryan Kearney wrote:
Can we break on the first sentence, not line So..
I did cool shite. Really, this is cool.
that way I can use commit -m
It's not a requirement :) I review all of the messages before committing the changelog and clean them up. I guess I could make tito smart to break on the first sentence.
+1 for smart tito.
-- bk
candlepin@lists.stg.fedorahosted.org