This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: git commit message conventions

From: Paul Eggert <eggert at cs dot ucla dot edu>
To: Joseph Myers <joseph at codesourcery dot com>, libc-alpha at sourceware dot org
Date: Tue, 02 Jun 2015 18:19:56 -0700
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>

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 youindent the entire commit message, and omit the 2nd (empty) line, the entirecommit message must be a valid ChangeLog entry. That way, there's a one-to-onerelationship between commit messages and ChangeLog entries, and programs likevc-dwim can be used to generate commits. Projects that use such a style includeCoreutils, Gnulib, and GNU Emacs. I suggest using it for glibc as well.

Follow-Ups:
- Re: git commit message conventions
  - From: Rich Felker
- Re: git commit message conventions
  - From: Torvald Riegel
- Re: git commit message conventions
  - From: Joseph Myers

References:
- git commit message conventions
  - From: Joseph Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]