This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: git commit message conventions
- From: Torvald Riegel <triegel at redhat dot com>
- To: Paul Eggert <eggert at cs dot ucla dot edu>
- Cc: Joseph Myers <joseph at codesourcery dot com>, libc-alpha at sourceware dot org
- Date: Wed, 03 Jun 2015 09:01:49 +0200
- Subject: Re: git commit message conventions
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 10 dot 1506022041430 dot 2704 at digraph dot polyomino dot org dot uk> <556E563C dot 1090204 at cs dot ucla dot edu>
On Tue, 2015-06-02 at 18:19 -0700, Paul Eggert wrote:
> Joseph Myers wrote:
> > I propose that we adopt standard git commit message conventions that: the
> > first line of a commit message is a short description of the commit, the
> > next line is a blank line, and the rest of the commit message is the
> > detailed description / rationale for the patch
>
> Many other GNU projects use this style, but with one further constraint: if you
> indent the entire commit message, and omit the 2nd (empty) line, the entire
> commit message must be a valid ChangeLog entry.
I'd much rather like to see the justification and motivation for the
patch (ie, what we're currently putting in the emails accompanying a
patch) be part of the git logs. I'm that this is not the same as a
Changelog entry's content, but it would be more valuable to me.