From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9223 invoked by alias); 8 Oct 2013 23:28:47 -0000 Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org Received: (qmail 9201 invoked by uid 89); 8 Oct 2013 23:28:47 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 08 Oct 2013 23:28:46 +0000 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1VTghm-0006pu-CZ from Iain_Sandoe@mentor.com ; Tue, 08 Oct 2013 16:28:42 -0700 Received: from SVR-IES-FEM-02.mgc.mentorg.com ([137.202.0.106]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 8 Oct 2013 16:28:42 -0700 Received: from [127.0.0.1] (137.202.0.76) by SVR-IES-FEM-02.mgc.mentorg.com (137.202.0.106) with Microsoft SMTP Server id 14.2.247.3; Wed, 9 Oct 2013 00:28:41 +0100 Subject: Re: src.git test repository MIME-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset="us-ascii" From: Iain Sandoe In-Reply-To: <87mwmlkojs.fsf@fleche.redhat.com> Date: Tue, 08 Oct 2013 23:28:00 -0000 CC: Binutils , GDB Development Content-Transfer-Encoding: quoted-printable Message-ID: References: <87y565m7ma.fsf@fleche.redhat.com> <87mwmlkojs.fsf@fleche.redhat.com> To: Tom Tromey X-SW-Source: 2013-10/txt/msg00097.txt.bz2 Hi Tom, thanks for doing this! On 7 Oct 2013, at 17:56, Tom Tromey wrote: > HJ> I noticed that binutils-2_24-branch only has binutils source. > HJ> How will binutils-2_25-branch be made? Will it include gdb > HJ> source? >=20 > It's up to the binutils developers. >=20 > What I recommend is branching the whole repository and then doing > tarball releases of a subset of the branch, using the usual src-release > mechanism. I had a go this evening (with success) doing the following: cloned src=20 built a sparse checkout by hand for 'binutils' and built a cross from x86-64-darwin12 -> powerpc-linux-gnu All seems OK, but I think I lost track of where the discussion had got to o= n sparse checkouts, building the .git/info/sparse-checkout file by hand is = tedious. somewhere to put the recipes/defaults corresponding to the existing checkou= ts would be handy. or did I miss it? Iain