From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29587 invoked by alias); 13 Oct 2011 22:45:09 -0000 Received: (qmail 29571 invoked by uid 22791); 13 Oct 2011 22:45:07 -0000 X-SWARE-Spam-Status: No, hits=-6.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_EG,TW_FC X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 13 Oct 2011 22:44:50 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9DMijWY000617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 13 Oct 2011 18:44:45 -0400 Received: from host1.jankratochvil.net (ovpn-116-16.ams2.redhat.com [10.36.116.16]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p9DMigHx016093 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Oct 2011 18:44:44 -0400 Received: from host1.jankratochvil.net (localhost [127.0.0.1]) by host1.jankratochvil.net (8.14.4/8.14.4) with ESMTP id p9DMig0P019606; Fri, 14 Oct 2011 00:44:42 +0200 Received: (from jkratoch@localhost) by host1.jankratochvil.net (8.14.4/8.14.4/Submit) id p9DMif1u019600; Fri, 14 Oct 2011 00:44:41 +0200 Date: Thu, 13 Oct 2011 22:45:00 -0000 From: Jan Kratochvil To: "Alfred M. Szmidt" Cc: pmuldoon@redhat.com, joseph@codesourcery.com, gdb@sourceware.org Subject: Re: GIT and CVS Message-ID: <20111013224440.GA17614@host1.jankratochvil.net> References: <20111013215020.GA13438@host1.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-10/txt/msg00094.txt.bz2 On Fri, 14 Oct 2011 00:19:17 +0200, Alfred M. Szmidt wrote: > While useful, they don't replace information of this type: > > * configure.ac (tic6x-*-*): Remove gdb from noconfigdirs. git log -p: tic6x-*-*) - noconfigdirs="$noconfigdirs gdb sim" + noconfigdirs="$noconfigdirs sim" git annotate: 005efcbe (Joseph Myers 2010-03-23 16:05:34 +0000 1022) tic6x-*-*) 34dd72a9 ( qiyao 2011-08-14 12:28:15 +0000 1023) noconfigdirs="$noconfigdirs sim" 005efcbe (Joseph Myers 2010-03-23 16:05:34 +0000 1024) ;; -> git show 34dd72a9 What's wrong with it? And if I search which commit changed it: git log -p -Sgdb configure.ac > You still have to store that information _somewhere_, be it in a file > or in the commit message. Still there should be stored + shown the associated mail which completely misses here and which is stored there by GIT. Currently I have to always look up the associated mails with each CVS commit to have the reasons and background of each patch; it is really a lose of engineering time looking up all the mails by hand I have to do with CVS: http://pkgs.fedoraproject.org/gitweb/?p=gdb.git;a=blob_plain;f=gdb-upstream.patch;hb=f16 -> ... FYI: implement new DWARF macro proposal http://sourceware.org/ml/gdb-patches/2011-07/msg00732.html http://sourceware.org/ml/gdb-cvs/2011-07/msg00212.html ... [patch][python] Fix sigsegv when a printer fails to return a value and string_print is set. http://sourceware.org/ml/gdb-patches/2011-07/msg00719.html http://sourceware.org/ml/gdb-cvs/2011-07/msg00234.html ... etc. > I just don't see how annotate/log replaces > that here, maybe it should? I don't know, but entries like that are > super useful to trace history of things. When I was a newbie to GDB I would not see the reason why string "gdb" was removed from variable "noconfigdirs". I would like to find out the mail submit/reasoning/approval. I tried now but I failed to find the mail. Contrary to it you can see the explanation of a commit in: http://git.kernel.org/?p=git/git.git;a=commit;h=d4e85a1afe0a3310a3c8336c2824775901cc27d7 It is true I would prefer URL / Message-ID for the mail thread, it is not commonly there even with GIT. There are some other patch management software for such tracking. Regards, Jan