+1 Anthony
> On Aug 5, 2015, at 3:18 PM, Kirk Lund <kl...@pivotal.io> wrote: > > Several of us were discussing http://chris.beams.io/posts/git-commit/ -- > there are a couple other really good articles about git commit messages and > below is the message style I've been trying to follow. > > http://chris.beams.io/posts/git-commit/ > http://www.laurencegellert.com/2013/07/how-to-write-a-proper-commit-message/ > http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html > > GEODE-nn: Begin capitalized and 50 chars or less > > More detailed explanation with linefeeds to wrap at 72 characters after > a blank line following the summary. > > Further paragraphs come after blank lines. > > - Bullet points are okay, too > > - Typically a hyphen or asterisk is used for the bullet, followed by a > single space, with blank lines in between, but conventions vary here > > - Use a hanging indent
