From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21433 invoked by alias); 2 Dec 2007 14:27:02 -0000 Received: (qmail 21425 invoked by uid 22791); 2 Dec 2007 14:27:02 -0000 X-Spam-Check-By: sourceware.org Received: from elasmtp-dupuy.atl.sa.earthlink.net (HELO elasmtp-dupuy.atl.sa.earthlink.net) (209.86.89.62) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 02 Dec 2007 14:26:50 +0000 Received: from [67.38.22.223] (helo=owl.gateway.2wire.net) by elasmtp-dupuy.atl.sa.earthlink.net with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1IypmS-0001Xh-I5 for gcc@gcc.gnu.org; Sun, 02 Dec 2007 09:26:48 -0500 Received: from kiesling by owl.gateway.2wire.net with local (Exim 4.63) (envelope-from ) id 1IypmO-0004j8-9s for gcc@gcc.gnu.org; Sun, 02 Dec 2007 09:26:44 -0500 Subject: Re: Rant about ChangeLog entries and commit messages In-Reply-To: <200712021405.16103.ebotcazou@libertysurf.fr> To: gcc@gcc.gnu.org Date: Sun, 02 Dec 2007 14:27:00 -0000 X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" Message-Id: From: Robert Kiesling X-ELNK-Trace: 0b901cbc512a9d8594f5150ab1c16ac01a238acc8405a5b0b93f970e17f8deebe5458422d3ee104f350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c 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/msg00031.txt.bz2 [ Charset ISO-8859-1 unsupported, converting... ] > > FWIW, I agree completely - I've never found ChangeLogs useful, I hate > > writing them, and I think the linux-kernel guys these days generally have > > much better checkin messages than we do. > > I guess nobody really loves writing ChangeLog entries, but in my opinion there > are quite effective "executive summaries" for the patches and helpful to the > reader/reviewer. Please let's not throw the baby with the bath's water. If there's a mechanism to filter checkin messages to ChangeLog summaries, I would be happy to use it - in cases of multiple packages, especially, it's important to know what changes were made, when, and when the changes propagated through packages and releases, and where they got to, occasionally. Anybody know of a useful, built-in mechanism for this task? -- Ctalk Home Page: http://ctalk-lang.sourceforge.net