From: brabuhr@...
Date: 2011-06-15T04:03:59+09:00
Subject: Re: commit message conventions

On Tue, Jun 14, 2011 at 1:47 PM, Phillip Gawlowski
<cmdjackryan@googlemail.com> wrote:
> On Tue, Jun 14, 2011 at 7:26 PM, Intransition <transfire@gmail.com> wrote:
>> The "parse history" could bare more explanation.
>
> It's left as an exercise to the reader, since it's highly dependent on
> the source control tool(s) you use. ;)
>
> But as an example:
>
> Mercurial has style templates[0], which allow customizing output of,
> for example, the "hg log" command, which allows outputting branch
> information for a given changeset.

With git, on the commit message side of things, you can use a template
to help standardize the messages, e.g.:
    [short subject here]

    [long description here]

    References
      * [ticket number]
      * [etc...]

On the log viewing side, git provides some canned output formats and
also a flexible format-string option.

git-log(1)
    format:"The author of %h was %an, %ar%nThe title was >>%s<<%n"
    would show something like this:
        The author of fe6e0ee was Junio C Hamano, 23 hours ago
        The title was >>t4119: test autocomputing -p<n> for
traditional diff input.<<

* http://spheredev.org/wiki/Git_for_the_lazy#Writing_good_commit_messages
* http://www.jukie.net/bart/blog/pimping-out-git-log