From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26006 invoked by alias); 14 Aug 2014 14:45:30 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 25975 invoked by uid 89); 14 Aug 2014 14:45:29 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx2.suse.de Received: from cantor2.suse.de (HELO mx2.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (CAMELLIA256-SHA encrypted) ESMTPS; Thu, 14 Aug 2014 14:45:27 +0000 Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 5872CAB07; Thu, 14 Aug 2014 14:45:24 +0000 (UTC) From: Andreas Schwab To: Joel Brobecker Cc: Gary Benson , Mike Frysinger , gdb@sourceware.org, Andreas Arnez Subject: Re: ChangeLogs in commit messages References: <20140814083231.GA6283@blade.nx> <6036430.RnprRWgZmF@vapier> <20140814131206.GA12746@blade.nx> <20140814132939.GH4924@adacore.com> <20140814134807.GI4924@adacore.com> <20140814142201.GJ4924@adacore.com> X-Yow: I think I'll make SCRAMBLED EGGS!! They're each in LITTLE SHELLS.. Date: Thu, 14 Aug 2014 14:45:00 -0000 In-Reply-To: <20140814142201.GJ4924@adacore.com> (Joel Brobecker's message of "Thu, 14 Aug 2014 07:22:01 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2014-08/txt/msg00031.txt.bz2 Joel Brobecker writes: > Again, I do think that having the CL entry in the commit message is > useful, and I disagree with the idea of removing it from there. > Imagine you are scanning the past changes, looking for what might > have caused a behavior change. When using "git log", having the CL > in there often helps. It's already included. You can use git log -p to show it. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."