From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25208 invoked by alias); 17 Jun 2008 20:58:19 -0000 Received: (qmail 25199 invoked by uid 22791); 17 Jun 2008 20:58:18 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout4.012.net.il (HELO mtaout4.012.net.il) (84.95.2.10) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 17 Jun 2008 20:57:53 +0000 Received: from conversion-daemon.i_mtaout4.012.net.il by i_mtaout4.012.net.il (HyperSendmail v2004.12) id <0K2M00900LG9K200@i_mtaout4.012.net.il> for gdb-patches@sourceware.org; Wed, 18 Jun 2008 00:10:20 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.229.217.57]) by i_mtaout4.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K2M008W9LH89000@i_mtaout4.012.net.il>; Wed, 18 Jun 2008 00:10:20 +0300 (IDT) Date: Wed, 18 Jun 2008 00:22:00 -0000 From: Eli Zaretskii Subject: Re: [non-stop] 01/10 Add "executing" property In-reply-to: <20080617182050.GA3595@adacore.com> X-012-Sender: halo1@inter.net.il To: Joel Brobecker Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: References: <200806152203.14626.pedro@codesourcery.com> <20080617055354.GA3803@adacore.com> <20080617182050.GA3595@adacore.com> 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/msg00326.txt.bz2 > Date: Tue, 17 Jun 2008 14:20:50 -0400 > From: Joel Brobecker > Cc: pedro@codesourcery.com, gdb-patches@sourceware.org > > > Well, "Makefile.in (foo): Update." doesn't give any idea WHAT was > > done, it only says WHERE it was done. > > Actually, it does, at least as far I what I want to know (I want to > know that the author did an update of the Makefile rules). That's exactly what "cvs log" tells you as well. > I don't remember checking exactly what dependencies were added or > removed, but I don't mind using CVS for that. It's a pain to do this with CVS, at least in the situations I have in mind. Imagine that you need to find all the changes in a certain part of a specific rule since a very old version. Perhaps you wonder why that part of the rule has its present shape, or what other files were modified together with that part of the rule, or who did those changes. "cvs annotate" only gives you the last version, and "cvs log" doesn't say _what_ was changed. The only way I know of is to use "cvs diff -rVn -rVn+1" until you have all the history figured out and find those changes that matter. The fact that the ChangeLog tells you the name of the rule is of little help, because you are still facing a lot of changes in the same rule, even if you now can skip some of the versions. By contrast, if the ChangeLog states what was changed in the rule, you can find the information you want or at least dramatically narrow the number of version diffs you need to review just by looking up the target's name in the log file, and then reading what was modified in the rule. I've been there quite a few times, and I came to appreciate a few details in the log entry.