From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18605 invoked by alias); 7 Oct 2013 16:56:27 -0000 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 Received: (qmail 18585 invoked by uid 89); 7 Oct 2013 16:56:27 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 07 Oct 2013 16:56:27 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r97GuOGN005988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 7 Oct 2013 12:56:25 -0400 Received: from barimba (ovpn-113-128.phx2.redhat.com [10.3.113.128]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r97GuNRV020128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 7 Oct 2013 12:56:23 -0400 From: Tom Tromey To: "H.J. Lu" Cc: Binutils Development , GDB Development Subject: Re: src.git test repository References: <87y565m7ma.fsf@fleche.redhat.com> Date: Mon, 07 Oct 2013 16:56:00 -0000 In-Reply-To: (H. J. Lu's message of "Mon, 7 Oct 2013 09:43:32 -0700") Message-ID: <87mwmlkojs.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-10/txt/msg00026.txt.bz2 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? It's up to the binutils developers. 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. Tom