Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: add version 2.23.1
Date: Thu, 15 Nov 2012 12:30:37 -0300	[thread overview]
Message-ID: <50A50A9D.8060507@zacarias.com.ar> (raw)
In-Reply-To: <CAFbHwiTmCbwarYSgnD7ZkRob7SOVK2T_4Obz6jCR5eJj75j=rA@mail.gmail.com>

On 11/15/2012 12:27 PM, Will Newton wrote:

> From the 2.23.1 release announcement:
> 
> "Thanks to everyone who contributed to the release. The branch remains
> open for bug fixes.
> 
> Note that because of packaging issues, binutils 2.23 was not released."
> 
> I'm not sure what the precise issues were but it seems safer to move to 2.23.1.

From what i've read in the mailing list there were some tagging issues
and whatnot.
There was also the vanishing tarball issue, when i sent the initial 2.23
bump there was a tar.bz2 for 2.23 and then it was gone with only the
tar.gz remaining.
I'm not for or against the move, since it's not a default i see no big
issue removing it, but then we always gave some choice regarding
toolchain components.
Regards.

  reply	other threads:[~2012-11-15 15:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 14:08 [Buildroot] [PATCH] binutils: add version 2.23.1 Gustavo Zacarias
2012-11-15 15:12 ` Peter Korsgaard
2012-11-15 15:16   ` Gustavo Zacarias
2012-11-15 15:17   ` Will Newton
2012-11-15 15:25     ` Gustavo Zacarias
2012-11-15 15:27       ` Will Newton
2012-11-15 15:30         ` Gustavo Zacarias [this message]
2012-11-15 15:39         ` Peter Korsgaard
2012-11-15 16:01           ` Gustavo Zacarias
2012-11-15 21:01             ` Peter Korsgaard

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=50A50A9D.8060507@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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