From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26536 invoked by alias); 16 Jun 2008 03:17:53 -0000 Received: (qmail 26526 invoked by uid 22791); 16 Jun 2008 03:17:52 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout1.012.net.il (HELO mtaout1.012.net.il) (84.95.2.1) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 16 Jun 2008 03:17:28 +0000 Received: from HOME-C4E4A596F7 ([84.228.242.237]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0K2J00FOBDU6TSQ0@i-mtaout1.012.net.il> for gdb-patches@sourceware.org; Mon, 16 Jun 2008 06:32:30 +0300 (IDT) Date: Mon, 16 Jun 2008 03:23:00 -0000 From: Eli Zaretskii Subject: Re: [non-stop] 01/10 Add "executing" property In-reply-to: <20080616012617.GA8944@caradoc.them.org> X-012-Sender: halo1@inter.net.il To: Daniel Jacobowitz Cc: pedro@codesourcery.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: Content-transfer-encoding: 7BIT References: <200806152203.14626.pedro@codesourcery.com> <20080616012617.GA8944@caradoc.them.org> 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/msg00301.txt.bz2 > Date: Sun, 15 Jun 2008 21:26:17 -0400 > From: Daniel Jacobowitz > Cc: Pedro Alves , gdb-patches@sourceware.org > > On Mon, Jun 16, 2008 at 12:47:43AM +0300, Eli Zaretskii wrote: > > > * Makefile.in (event-top.o, frame.o, inf-loop.o, top.o): > > > Update. > > > > I think you should tell what prerequisites were added to each target. > > A simple "update" will never reveal when a prerequisite was added, if > > someone will ever want to know. > > I don't think it's necessary to duplicate the contents of the patch in > the changelog. How else would one know when a certain change was done to a certain file? For that matter, why do we bother writing log entries at all? > 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.