public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: Release 2.21.1 ?
Date: Tue, 15 Mar 2011 13:24:00 -0000	[thread overview]
Message-ID: <mcr62rkzfeg.fsf@google.com> (raw)
In-Reply-To: <D27CC4D0-B7AF-4D15-9BDB-D52B3C12DAC4@adacore.com> (Tristan	Gingold's message of "Tue, 15 Mar 2011 09:21:37 +0100")

Tristan Gingold <gingold@adacore.com> writes:

> now that gcc 4.6 is released, I'd like to know if binutils developers want a new binutils release.

I would like to see a binutils 2.21.1 release at some point.

Ian

  reply	other threads:[~2011-03-15 13:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15  8:21 Tristan Gingold
2011-03-15 13:24 ` Ian Lance Taylor [this message]
2011-03-15 17:28 ` Jakub Jelinek
2011-03-15 17:30 ` Matthias Klose
2011-03-15 17:51   ` Dave Korn
2011-03-16  7:52     ` Tristan Gingold
2011-03-16  4:03 ` Mike Frysinger
2011-03-16  8:49   ` Tristan Gingold
2011-03-16 12:19     ` Alan Modra
2011-03-17 12:21     ` Alan Modra
2011-03-17 12:39       ` Tristan Gingold
2011-03-20 21:41 ` Mike Frysinger
2011-03-23 16:00   ` Tristan Gingold
2011-05-16  7:47 ` Andreas Krebbel
2011-05-16  7:53   ` Tristan Gingold
2011-05-17 17:31     ` Andreas Krebbel
2011-05-18  7:03       ` Tristan Gingold
2011-05-16 10:05   ` Marek Polacek
2011-05-26  7:54 ` Release 2.21.1 [again] Tristan Gingold
2011-05-29  7:57   ` Alan Modra
2011-05-29 17:18     ` Alan Modra
2011-05-29 17:26     ` Alan Modra
2011-05-29 20:55     ` Alan Modra
2011-03-16  6:44 Release 2.21.1 ? Sedat Dilek
2011-03-16  8:50 ` Tristan Gingold
2011-03-16  9:37   ` Sedat Dilek
2011-03-16 15:34     ` Sedat Dilek
2011-03-16 12:17   ` Alan Modra
2011-03-16 12:44     ` H.J. Lu
2011-03-16 12:47       ` 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=mcr62rkzfeg.fsf@google.com \
    --to=iant@google.com \
    --cc=binutils@sourceware.org \
    --cc=gingold@adacore.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).