From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 82506 invoked by alias); 7 Nov 2019 14:27:31 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 82498 invoked by uid 89); 7 Nov 2019 14:27:30 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=our, HContent-Transfer-Encoding:8bit X-HELO: snark.thyrsus.com Received: from thyrsus.com (HELO snark.thyrsus.com) (71.162.243.5) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 07 Nov 2019 14:27:28 +0000 Received: by snark.thyrsus.com (Postfix, from userid 1000) id 3473A4704893; Thu, 7 Nov 2019 09:27:27 -0500 (EST) Date: Thu, 07 Nov 2019 14:27:00 -0000 From: "Eric S. Raymond" To: Jeff Law Cc: "Richard Earnshaw (lists)" , GCC Development Subject: Re: Commit messages and the move to git Message-ID: <20191107142727.GA72444@thyrsus.com> Reply-To: esr@thyrsus.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-IsSubscribed: yes X-SW-Source: 2019-11/txt/msg00065.txt.bz2 Jeff Law : > On 11/4/19 3:29 AM, Richard Earnshaw (lists) wrote: > > With the move to git fairly imminent now it would be nice if we could > > agree on a more git-friendly style of commit messages; and, ideally, > > start using them now so that the converted repository can benefit from > > this. > > > > Some tools, particularly gitk or git log --oneline, can use one-line > > summaries from a commit's log message when listing commits.  It would be > > nice if we could start adopting a style that is compatible with this, so > > that in future commits are summarized in a useful way.  Unfortunately, > > some of our existing commits show no useful information with tools like > > this. > I'd suggest we sync policy with glibc. They're further along on the > ChangeLog issues. Whatever they do in this space we should follow -- > aren't we going to be using some of their hooks/scripts? Note that my reposurgeon conversion recipe runs gitify on the repository. >From the documentation: Attempt to massage comments into a git-friendly form with a blank separator line after a summary line. This code assumes it can insert a blank line if the first line of the comment ends with '.', ',', ':', ';', '?', or '!'. If the separator line is already present, the comment won't be touched. Takes a selection set, defaulting to all commits and tags. -- Eric S. Raymond