From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18004 invoked by alias); 13 Oct 2011 22:19:47 -0000 Received: (qmail 17995 invoked by uid 22791); 13 Oct 2011 22:19:46 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (140.186.70.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 13 Oct 2011 22:19:19 +0000 Received: from ams by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1RETcT-0001Np-8Y; Thu, 13 Oct 2011 18:19:17 -0400 Date: Thu, 13 Oct 2011 22:19:00 -0000 Message-Id: From: ams@gnu.org (Alfred M. Szmidt) To: Jan Kratochvil CC: pmuldoon@redhat.com, joseph@codesourcery.com, gdb@sourceware.org In-reply-to: <20111013215020.GA13438@host1.jankratochvil.net> (message from Jan Kratochvil on Thu, 13 Oct 2011 23:50:20 +0200) Subject: Re: GIT and CVS Reply-to: ams@gnu.org References: <20111013215020.GA13438@host1.jankratochvil.net> 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/msg00090.txt.bz2 > Could you explain how `git log' replaces ChangeLog? It doesn't do > much more than what `cvs log' does, so you still need to write > which function/variable was modified, and git log doesn't do that > as far as I know (it only lists which files, and how many lines > where added/delete which isn't very useful). You have primarily `git annotate [revision]' which is like `cvs annotate' but with the speed of GIT you can really use it. You have also `git log -S [-p]' where you can filter patches on specific text changes, it is also very fast. While useful, they don't replace information of this type: * configure.ac (tic6x-*-*): Remove gdb from noconfigdirs. You still have to store that information _somewhere_, be it in a file or in the commit message. 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. As a side node, Coreutils stores "ChangeLog entries" in the commit message, and dumps it to disk when they make a release. It seems to work well for them.