This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: git commit message conventions
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: Paul Eggert <eggert at cs dot ucla dot edu>
- Cc: Torvald Riegel <triegel at redhat dot com>, Joseph Myers <joseph at codesourcery dot com>, libc-alpha at sourceware dot org
- Date: Thu, 04 Jun 2015 14:18:39 +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> <1433314909 dot 21461 dot 65 dot camel at triegel dot csb> <556ECDF8 dot 1040107 at redhat dot com> <556F3B42 dot 10406 at cs dot ucla dot edu>
* Paul Eggert:
> Florian Weimer wrote:
>> I completely agree, and I think Joseph's proposal goes in that direction.
>
> Then I'm afraid I misread the direction of the proposal.
>
> I don't much care about whether the commit message uses ChangeLog
> format or some other format.
Agreed, that's not a useful conversation to have.
> What I find puzzling, though, is the implication that the commit
> message should differ from the change log and that each should have
> its own specialized format.
As far as I understand them, the GNU Coding Standards do not permit
the information we want to associate with each commit in ChangeLog
files. Hence the need for separation.