From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21296 invoked by alias); 3 Dec 2007 18:20:05 -0000 Received: (qmail 21280 invoked by uid 22791); 3 Dec 2007 18:20:04 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 03 Dec 2007 18:19:53 +0000 Received: from zps35.corp.google.com (zps35.corp.google.com [172.25.146.35]) by smtp-out.google.com with ESMTP id lB3IJmO2007711 for ; Mon, 3 Dec 2007 10:19:48 -0800 Received: from an-out-0708.google.com (anab33.prod.google.com [10.100.53.33]) by zps35.corp.google.com with ESMTP id lB3IJjuG015649 for ; Mon, 3 Dec 2007 10:19:47 -0800 Received: by an-out-0708.google.com with SMTP id b33so773151ana for ; Mon, 03 Dec 2007 10:19:45 -0800 (PST) Received: by 10.100.44.4 with SMTP id r4mr20717946anr.1196705985286; Mon, 03 Dec 2007 10:19:45 -0800 (PST) Received: from frodo.local ( [72.14.224.1]) by mx.google.com with ESMTPS id d12sm6318615and.2007.12.03.10.19.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 03 Dec 2007 10:19:44 -0800 (PST) Message-ID: <475448BC.2020103@google.com> Date: Mon, 03 Dec 2007 18:20:00 -0000 From: Diego Novillo User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Bernd Schmidt CC: Samuel Tardieu , gcc@gcc.gnu.org, Daniel Berlin Subject: Re: Rant about ChangeLog entries and commit messages References: <2007-12-02-11-05-39+trackit+sam@rfc1149.net> <47543DE8.3010003@google.com> <475440E8.4000109@t-online.de> In-Reply-To: <475440E8.4000109@t-online.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 X-SW-Source: 2007-12/txt/msg00087.txt.bz2 Bernd Schmidt wrote: > I'd much prefer the text from the mail message be repeated in the commit > log. Removes one step of indirection both when writing and reading the log. I guess that could work, but that wouldn't give a way into the history for the change. Several times there is a post-mortem discussion on the patch, leading to more patches. Diego.