From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31276 invoked by alias); 16 Jun 2008 03:36:08 -0000 Received: (qmail 31268 invoked by uid 22791); 16 Jun 2008 03:36:07 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 16 Jun 2008 03:35:33 +0000 Received: from kahikatea.snap.net.nz (169.61.255.123.dynamic.snap.net.nz [123.255.61.169]) by viper.snap.net.nz (Postfix) with ESMTP id 94ABB2F40A1; Mon, 16 Jun 2008 15:35:31 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 94FDA8FC6D; Mon, 16 Jun 2008 15:35:16 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18517.57202.90761.74048@kahikatea.snap.net.nz> Date: Mon, 16 Jun 2008 06:45:00 -0000 To: Eli Zaretskii Cc: Daniel Jacobowitz , pedro@codesourcery.com, gdb-patches@sourceware.org Subject: ChangeLog entries [was Re: [non-stop] 01/10 Add "executing" property] In-Reply-To: References: <200806152203.14626.pedro@codesourcery.com> <20080616012617.GA8944@caradoc.them.org> X-Mailer: VM 7.19 under Emacs 22.2.50.2 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-06/txt/msg00305.txt.bz2 > > Do you really think it's useful? We've never asked to > > do this (see the cvs log of Makefile.in for plenty of examples), and I > > would resist; changelogs already take a long time to write. > > It's common practice in GNU projects. I'm quite shocked to learn that > some of us resist it. Yes, our log entries are already quite sloppy > and unhelpful, but there are limits. I find the ChangeLog useful as a starting point to understand when and why changes to individual files were made. It's probably hard to prescribe _exactly_ what should go in but I've never looked at a ChangeLog to understand when and why a dependency was added to a Makefile. So I'm inclined to agree with Daniel. It's pretty straightforward to determine whether a dependency is needed or not - no need to go trawling through the CVS history. -- Nick http://www.inet.net.nz/~nickrob