This post is on how to write a commit message.
From: Linus Torvalds <email@example.com>
Subject: Re: [PATCH] Bugfix to commit
Date: Tue, 23 Oct 2007 15:53:41 UTC
On Tue, 23 Oct 2007, Olaf Hering wrote:
> On Mon, Oct 22, Grant Likely wrote:
> > Olaf, do I have the correct solution here?
Side note: I already applied that patch, but take a look at the commit
That’s right: I had to edit the message provided to make it readable. So
I’ll just take this opportunity to ask people that when they send
bug-fixes, please try to make the subject line and message make sense for
a *reader*, not for yourself (or even to me, although if it’s readable to
some generic person, it’s hopefully readable to me too!).
So a subject line of “Bugfix to commit <commit-sha-goes-here>” is
obviously not a very nice one, if you’re looking at the kernel commit
history in gitk or some other visualizer that shows the first line as the
subject for the whole commit. It just doesn’t make any sense to the
Related to that, another thing that also happens is that people write
subject lines (and the description) as if everybody realized that
something is particular to that architecture or driver. It may be true
that that particular developer (or development list) is only about ppc,
and then people write subject lines like “Fix execve() argument handling”,
but again, when a *generic* person reads that, it now reads totally wrong,
since it wasn’t execve() in general, it was a particular architecture that
it went wrong for.
So the rule should be:
– if it’s not fairly generic, specify the area (architecture, subsystem,
driver) that the fix is for in the subject line. Even if you end up
initially sending the fix out to just a list that handles that
particular subsystem anyway.
– don’t use commit names in the subject line – and while it’s great to
use them in the body of the explanation, even there you don’t want to
assume that people read it from within git. People see patches and
commit changelogs on the web or the commit mailing lists, so when
specifying an exact version, also specify the human-readable name of
– write the commit message for an outsider, and use whitespace. The
third-most common fixup I end up doing (after the above two) is to
split things up into shorter paragraphs, after somebody wrote a good
changelog entry, but made it one large unreadable blob of text. The
more involved and technical some description is (and that’s what long
changelog entries should be – we don’t want a fluffy novella here!),
the more “breather space” and individually understandable small
snippets of text readers need. Making things too dense is bad.
Anyway, this was in no way meant to be a specific problem for Grant or
Olaf – I end up editing just about half of all the commit messages of
stuff I get in email (except for Andrew’s stuff, since Andrew largely does
the same kinds of cleanups anyway, so I only need to edit up a small
percentage of the patches he forwards). I’d like it to be *much* less than
that, so I thought I should speak up since I had an example of this.
This has some more interesting stuff. 🙂