From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26403 invoked by alias); 17 Jun 2008 05:54:52 -0000 Received: (qmail 26393 invoked by uid 22791); 17 Jun 2008 05:54:51 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 17 Jun 2008 05:54:19 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 8C6D42ACFAF; Tue, 17 Jun 2008 01:54:17 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kdb-EztgKIbx; Tue, 17 Jun 2008 01:54:17 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 25B792ACFA7; Tue, 17 Jun 2008 01:54:16 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id A33D4E7ACD; Mon, 16 Jun 2008 22:53:54 -0700 (PDT) Date: Tue, 17 Jun 2008 16:14:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: Pedro Alves , gdb-patches@sourceware.org Subject: Re: [non-stop] 01/10 Add "executing" property Message-ID: <20080617055354.GA3803@adacore.com> References: <200806152203.14626.pedro@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i 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/msg00316.txt.bz2 > > * 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 can only speak for myself, but in my few years of GDB development, I have never missed having the exact dependencies in the ChangeLog. I really like concise ChangeLogs because they tell me what files were modified as part of a change set, and also give me a very rough idea of what was done inside each file. When the ChangeLog becomes too verbose, it becomes more difficult for me to use them. -- Joel