From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29066 invoked by alias); 25 Jun 2009 21:45:05 -0000 Received: (qmail 28987 invoked by uid 22791); 25 Jun 2009 21:45:04 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 25 Jun 2009 21:44:52 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n5PLgoM6007914; Thu, 25 Jun 2009 17:42:50 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n5PLgn2m008825; Thu, 25 Jun 2009 17:42:49 -0400 Received: from opsy.redhat.com (vpn-13-18.rdu.redhat.com [10.11.13.18]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n5PLgkJZ024203; Thu, 25 Jun 2009 17:42:47 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id B179C3785DB; Thu, 25 Jun 2009 15:42:45 -0600 (MDT) To: "Joseph S. Myers" Cc: gdb@sourceware.org Subject: Re: What is keeping GDB in CVS ? References: <87r5xgqk0k.wl%naesten@gmail.com> <20090619162308.GA13968@caradoc.them.org> <20090619162801.GA14773@caradoc.them.org> <20090619163753.GA9700@ednor.casa.cgf.cx> <20090619192236.GA10670@ednor.casa.cgf.cx> <20090620184837.GA866@ednor.casa.cgf.cx> From: Tom Tromey Reply-To: tromey@redhat.com Date: Thu, 25 Jun 2009 21:45:00 -0000 In-Reply-To: (Joseph S. Myers's message of "Sat\, 20 Jun 2009 19\:19\:46 +0000 \(UTC\)") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: 2009-06/txt/msg00244.txt.bz2 >>>>> "Joseph" == Joseph S Myers writes: Joseph> It seems quite clear to me that all these files should be automatically Joseph> tagged when the projects using them are tagged and branched when those Joseph> projects are branched and the tagged or branched versions should be Joseph> checked out automatically when the tag or branch is checked out. I looked into the situation a bit more. My understanding is that the git "submodules" feature only works for subdirectories of the tree. It would not therefore work directly for 'src', due to the top-level configury. It could be made to work, by requiring some pre-configure command to make symlinks or shuffle files around. I still think the best approach is to have a single "infra" repository holding the shared bits, which is then merged as-needed into other repositories. But, there are even issues with this. One is, what history do we use to initially populate this repository? (Maybe it doesn't matter due to all the double commits.) The other is, this would require changes to how gcc handles this code; and since gcc uses svn I suppose (but don't know for sure) that it would be a pain. I haven't looked into the "repo" tool that Jan mentioned, yet. Tom