From: brabuhr@...
Date: 2011-06-13T22:13:06+09:00
Subject: Re: commit message conventions

On Mon, Jun 13, 2011 at 7:58 AM, John Feminella <johnf@bitsbuilder.com> wrote:
> I greatly dislike that style, to be frank. My commit messages usually
> take this form:
>
> =====
> [short, one-line description of what the commit achieves written in
> present tense] [metadata, typically referencing a ticket number]
> [skip a line here]
> [optional commit body to explain the commit in more detail or to
> describe new conventions introduced, considerations, etc.]
> =====

git-commit(1)
    Though not required, it’s a good idea to begin the commit
    message with a single short (less than 50 character) line
    summarizing the change, followed by a blank line and then a
    more thorough description. Tools that turn commits into email,
    for example, use the first line on the Subject: line and the rest
    of the commit in the body.