From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5637 invoked by alias); 22 Nov 2013 03:02:03 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 5613 invoked by uid 89); 22 Nov 2013 03:02:01 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RDNS_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mail-ob0-f181.google.com Received: from Unknown (HELO mail-ob0-f181.google.com) (209.85.214.181) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 22 Nov 2013 03:02:00 +0000 Received: by mail-ob0-f181.google.com with SMTP id uy5so720204obc.12 for ; Thu, 21 Nov 2013 19:01:52 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.60.39.67 with SMTP id n3mr8522138oek.2.1385089312446; Thu, 21 Nov 2013 19:01:52 -0800 (PST) Received: by 10.76.171.1 with HTTP; Thu, 21 Nov 2013 19:01:52 -0800 (PST) In-Reply-To: <20131122021904.GN3481@adacore.com> References: <2741C968-721F-46E9-A2BA-E4B0F64C444B@adacore.com> <20130918213245.GO3132@adacore.com> <20131118172117.GD3481@adacore.com> <20131122021904.GN3481@adacore.com> Date: Fri, 22 Nov 2013 03:28:00 -0000 Message-ID: Subject: Re: Release 2.24 From: "H.J. Lu" To: Joel Brobecker Cc: "Maciej W. Rozycki" , Tom Tromey , Tristan Gingold , Richard Sandiford , Binutils , GDB Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes X-SW-Source: 2013-11/txt/msg00668.txt.bz2 On Thu, Nov 21, 2013 at 6:19 PM, Joel Brobecker wrote: >> Although if you expect the delay between binutils 2.24 and GDB 7.7 to >> stay within a couple weeks, e.g. if you think you'll be able to roll the >> latter out by say mid December, > > We might be able to achieve that timeframe, but it would be very hard > for me to guaranty it. From past experience, event if we started today, > I don't remember any release cycle that took less than a month so > we are already looking at a Xmas release at best. > > Here is what I propose: > > . Let's confirm the list of patches needed for the 7.6 branch > (is there just the one in binutils?) > > . Get them approved, and pushed to the gdb_7_6-branch > > . I will need from you a small description of what this release > is about. It will save me time and make sure I also don't say > something incorrect if I can just copy/paste that text directly > in the web + email announcements. > > . Once that's done, I have 2 options: > > (1) Create the new relase off the git repository, but create > the release either manually or with the new scripts; > Create a tarball from git is very straight forward. I put .gitattribues: https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=.gitattributes;h=15caafcf45711c658217db66862e93e56615e31a;hb=refs/heads/hjl/linux/applied on hjl/linux/applied branch for Linux binutils to ignore GDB files. I created a tag for release 2.24.51.0.1: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=2fba13a799a2f6550595247ae8fe35bac016485d Then I do # git archive --format=tar --prefix=binutils/ hjl/linux/release/2.24.51.0.1 > binutils-2.24.41.0.1.tar It creates a tarball for my binutils release. You just need a different .gitattribues for GDB, -- H.J.