This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Release 2.24
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: "Maciej W. Rozycki" <macro at codesourcery dot com>, Tom Tromey <tromey at redhat dot com>, Tristan Gingold <gingold at adacore dot com>, Richard Sandiford <rdsandiford at googlemail dot com>, Binutils <binutils at sourceware dot org>, GDB <gdb-patches at sourceware dot org>
- Date: Thu, 21 Nov 2013 19:01:52 -0800
- Subject: Re: Release 2.24
- Authentication-results: sourceware.org; auth=none
- References: <2741C968-721F-46E9-A2BA-E4B0F64C444B at adacore dot com> <BB32BE2A-A3CC-494C-9FB2-CFD322F49EA3 at adacore dot com> <alpine dot DEB dot 1 dot 10 dot 1309182134580 dot 4379 at tp dot orcam dot me dot uk> <20130918213245 dot GO3132 at adacore dot com> <alpine dot DEB dot 1 dot 10 dot 1309182238430 dot 4379 at tp dot orcam dot me dot uk> <alpine dot DEB dot 1 dot 10 dot 1311181646080 dot 21686 at tp dot orcam dot me dot uk> <20131118172117 dot GD3481 at adacore dot com> <alpine dot DEB dot 1 dot 10 dot 1311211718410 dot 21686 at tp dot orcam dot me dot uk> <20131122021904 dot GN3481 at adacore dot com>
On Thu, Nov 21, 2013 at 6:19 PM, Joel Brobecker <brobecker@adacore.com> 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.