public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: binutils 2.21.1 release?
Date: Tue, 01 Feb 2011 10:39:00 -0000	[thread overview]
Message-ID: <47D55B89-5257-4CBB-B41F-34BBF12CF69A@adacore.com> (raw)
In-Reply-To: <20110201023047.GO9489@bubble.grove.modra.org>


On Feb 1, 2011, at 3:30 AM, Alan Modra wrote:

> Is a 2.21.1 release planned soon?

Not soon.  I even wasn't sure to do a 2.21.1 release, as nobody asked and there weren't any major regression.

But I like the idea of making one that coincide with GCC 4.6.0, as suggested by DaveK (unless 2.22 comes before).

> How do you feel about the following collection of backports?

Long list :-)  But I am ok with that.  Will you take care of backporting ?

>  This
> brings non-target parts of 2.21 reasonably up to date with current
> mainline, with the exception of gold.  Some of the patches don't do
> much (formatting, refactoring) but the idea behind applying them is
> simply to make it easier to apply later mainline patches on 2.21.

Ok.

> I've mostly avoided target-specific patches because I figure it's up
> to target maintainers to push them as they see necessary.

Ok.

> The bug fixes I really want to see in a 2.21.1 release are my fixes to
> ld script expression handling.

Ok.

Tristan.

  parent reply	other threads:[~2011-02-01 10:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01  2:31 Alan Modra
2011-02-01  4:03 ` Dave Korn
2011-02-01 10:39 ` Tristan Gingold [this message]
2011-02-01 12:26   ` Alan Modra

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=47D55B89-5257-4CBB-B41F-34BBF12CF69A@adacore.com \
    --to=gingold@adacore.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    /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).