From: Tristan Gingold <gingold@adacore.com>
To: Richard Earnshaw <rearnsha@arm.com>
Cc: Matthias Klose <doko@ubuntu.com>,
"nickc@redhat.com" <nickc@redhat.com>,
binutils Development <binutils@sourceware.org>
Subject: Re: Release 2.23
Date: Wed, 01 Aug 2012 14:35:00 -0000 [thread overview]
Message-ID: <E776E417-18E2-42F4-877B-22189B1D0E70@adacore.com> (raw)
In-Reply-To: <50193705.1060103@arm.com>
On Aug 1, 2012, at 4:02 PM, Richard Earnshaw wrote:
>> As it might change the schedule, I'd like to understand the reasons for having aarch64 in 2.23
> Because binutils is a key enabler and rolling this out into various
> distros is significantly harder if it isn't in a major release. In
> particular we're targetting GCC-4.8 for the main compiler support and
> that needs a binutils that supports it.
Looks like a good rational, but this opens other possibilities:
* would it be acceptable to add aarch64 only in 2.23.1 (in case the submission takes time) ?
* if aarch64 comes only with 2.24, what would be the ideal schedule for the release ?
> Why are we planning a binutils release so much earlier this year than we
> have done for the previous 3 or 4 years (at least)?
I plan a release when the trunk is relatively quiet and when I have enough time for it.
Traditionally, the major release is planed for end of summer but we often slip a while :-)
Tristan.
next prev parent reply other threads:[~2012-08-01 14:35 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 12:41 Tristan Gingold
2012-07-31 20:30 ` Matthias Klose
2012-08-01 8:54 ` Richard Earnshaw
2012-08-01 13:59 ` Tristan Gingold
2012-08-01 14:03 ` Richard Earnshaw
2012-08-01 14:35 ` Tristan Gingold [this message]
2012-08-01 14:40 ` Richard Earnshaw
2012-08-02 11:41 ` Tristan Gingold
2012-08-31 14:40 ` Release 2.23: Ping Tristan Gingold
2012-08-31 14:46 ` Jan Beulich
2012-08-31 17:45 ` Tristan Gingold
2012-08-31 18:09 ` Mike Frysinger
2012-09-03 7:51 ` Tristan Gingold
2012-09-04 3:54 ` Mike Frysinger
2012-09-04 13:31 ` Tristan Gingold
2012-09-04 14:20 ` H.J. Lu
2012-09-04 14:31 ` H.J. Lu
2012-09-04 14:37 ` Tristan Gingold
2012-09-04 14:39 ` H.J. Lu
[not found] ` <alpine.DEB.1.10.1208312249380.12630@tp.orcam.me.uk>
2012-09-03 7:50 ` Tristan Gingold
2012-09-03 15:07 ` Maciej W. Rozycki
2012-09-03 15:18 ` Tristan Gingold
2012-09-04 14:45 ` Tristan Gingold
2012-09-04 16:31 ` Maciej W. Rozycki
2012-09-05 0:56 ` Maciej W. Rozycki
2012-09-05 8:54 ` Matthew Gretton-Dann
2012-09-05 9:04 ` Tristan Gingold
2012-09-05 10:59 ` Matthew Gretton-Dann
2012-09-05 12:02 ` Maciej W. Rozycki
2012-09-05 16:50 ` Richard Earnshaw
2012-09-05 20:48 ` Maciej W. Rozycki
2012-09-06 7:14 ` Tristan Gingold
2012-09-18 14:47 ` Maciej W. Rozycki
2012-09-13 17:36 ` Matthias Klose
2012-09-13 18:13 ` Maciej W. Rozycki
2012-09-14 6:58 ` Alan Modra
2012-09-14 8:21 ` Tristan Gingold
2012-09-14 17:05 ` Matthias Klose
2012-09-18 14:44 ` Maciej W. Rozycki
2012-09-03 15:09 ` Maciej W. Rozycki
2012-09-04 13:35 ` Tristan Gingold
2012-09-04 13:42 ` H.J. Lu
2012-09-04 13:51 ` Tristan Gingold
2012-09-04 13:58 ` Tristan Gingold
2012-09-05 9:02 ` Release 2.23: Ping #2 Tristan Gingold
2012-09-07 3:14 ` Alan Modra
2012-09-09 17:05 ` Hans-Peter Nilsson
2012-09-18 15:51 ` Release 2.23: Ping #3 Tristan Gingold
2012-09-18 15:54 ` H.J. Lu
2012-09-19 15:43 ` H.J. Lu
2012-09-24 12:23 ` Tristan Gingold
2012-08-01 15:50 ` Release 2.23 Mike Frysinger
2012-08-02 8:11 ` nick clifton
2012-08-01 14:50 ` Maciej W. Rozycki
2012-09-09 14:15 ` Matthias Klose
2012-09-09 14:48 ` Alan Modra
2012-09-10 15:16 ` Matthias Klose
2012-09-10 22:33 ` Alan Modra
2012-11-05 10:48 ` Alan Modra
2012-11-05 12:27 ` Alan Modra
2012-09-10 7:48 ` Tristan Gingold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E776E417-18E2-42F4-877B-22189B1D0E70@adacore.com \
--to=gingold@adacore.com \
--cc=binutils@sourceware.org \
--cc=doko@ubuntu.com \
--cc=nickc@redhat.com \
--cc=rearnsha@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).