Den 2013-04-08 18:47:38 skrev Dana Jansens <
dan...@chromium.org>:
> On Mon, Apr 8, 2013 at 9:41 AM, Torne (Richard Coles)
> <
to...@google.com>wrote:
>
>> Sure, but the default git log output still indents by four spaces, so if
>> we care about wrapping *anywhere*, we should wrap at no more than 76 :)
>>
>
> 72 keeps reverts from going over 80 col, since they are indented further.
If Blink is going to use git, it seems best to use the git conventions for
commit messages. Those are:
----------
Summary line with a max length of about 50 characters
Then an empty line followed by a longer description with a max length
of about 72 character. The 50 character limit is because that line is
often combined with dates, author names and other supplementary data
in logs or other tools. The 72 character length is, as others have said,
to allow a limited indentation without getting too long.
You can also read here or at several other similar places:
http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
----------
/Daniel