git commit message conventions

[Joseph Myers]

On Tue, 2 Jun 2015, Paul Eggert wrote:

> 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.  That way, there's a
> one-to-one relationship between commit messages and ChangeLog entries, and
> programs like vc-dwim can be used to generate commits.  Projects that use such
> a style include Coreutils, Gnulib, and GNU Emacs.  I suggest using it for
> glibc as well.

I propose that at this point we specifically do not adopt any further 
conventions regarding how commit messages relate to ChangeLog entries 
(including any conventions for how, if the ChangeLog entries are included 
in the commit messages at all, the authors for those entries are 
represented if not the same as the single commit author, or for how the 
ChangeLog entries for the three different ChangeLog files in current use 
are distinguished).  That is, we only require the substantive patch 
writeup to be included without making requirements that would allow any 
form of automatic processing into ChangeLog entries.

-- 
Joseph S. Myers
joseph@codesourcery.com