From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13075 invoked by alias); 14 Oct 2011 05:03:20 -0000 Received: (qmail 13062 invoked by uid 22791); 14 Oct 2011 05:03:18 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 14 Oct 2011 05:02:51 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id C5B432BB523; Fri, 14 Oct 2011 01:02:50 -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 Kgzx356MjvXb; Fri, 14 Oct 2011 01:02:50 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 7BCC32BB521; Fri, 14 Oct 2011 01:02:50 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 34BDD145615; Fri, 14 Oct 2011 01:02:45 -0400 (EDT) Date: Fri, 14 Oct 2011 05:03:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: Jan Kratochvil , joseph@codesourcery.com, pmuldoon@redhat.com, gdb@sourceware.org Subject: Re: GIT and CVS Message-ID: <20111014050245.GC18867@adacore.com> References: <20111013215927.GA13931@host1.jankratochvil.net> <83mxd41qu4.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83mxd41qu4.fsf@gnu.org> User-Agent: Mutt/1.5.20 (2009-06-14) 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/msg00101.txt.bz2 > The issue is how to > save the committers the need to compose 2 different logs, one for the > commit, the other for the ChangeLog. This issue should be resolved by > the VCS front end in use, like Emacs or whatever people use. When > such solutions exist, it is no longer an important issue whether to > keep ChangeLog's in the repo or generate them as needed. One problem that you are not mentioning is the fact that the ChangeLog causes a never-ending stream of conflicts when applying patches. This is because of how things are setup: We keep modifying the file at the same place. ChangeLogs were interesting at a time when VCS where limited, but we've abolished them at AdaCore ever since we moved our GDB development to Git. The cost of maintaining them versus the actual benefits was just too high. -- Joel