From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] Update binutils package
Date: Mon, 31 Jul 2017 21:29:24 +0200 [thread overview]
Message-ID: <20170731192924.GH31395@waldemar-brodkorb.de> (raw)
In-Reply-To: <20170731212753.5ab4e326@windsurf.home>
Hi,
Thomas Petazzoni wrote,
> Hello,
>
> On Sat, 29 Jul 2017 15:09:02 +0200, Thomas Petazzoni wrote:
>
> > Thomas Petazzoni (4):
> > binutils: bump 2.28.x series to 2.28.1
> > binutils: add support for binutils 2.29
>
> I've applied those ones, which I believe are not controversial/
>
> > binutils: switch to use 2.28.x as the default version
> > binutils: remove support for 2.26
>
> I'll hold off on those ones until I get some feedback, to decide
> whether we take them in 2017.08, or wait for 2017.11.
Having 2.28.1 as default seems okay to me.
I use 2.28 mostly and have seen no issues so far.
With binutils 2.29 I have some more issues for glibc toolchains.
I think tomorrow glibc developers will release their next version,
would it make sense to sent a patch or should I wait until
-next is open?
best regards
Waldemar
next prev parent reply other threads:[~2017-07-31 19:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 13:09 [Buildroot] [PATCH 0/4] Update binutils package Thomas Petazzoni
2017-07-29 13:09 ` [Buildroot] [PATCH 1/4] binutils: bump 2.28.x series to 2.28.1 Thomas Petazzoni
2017-07-29 13:09 ` [Buildroot] [PATCH 2/4] binutils: add support for binutils 2.29 Thomas Petazzoni
2017-07-29 18:15 ` Waldemar Brodkorb
2017-07-29 19:34 ` Thomas Petazzoni
2017-08-02 18:43 ` Max Filippov
2017-07-29 13:09 ` [Buildroot] [PATCH 3/4] binutils: switch to use 2.28.x as the default version Thomas Petazzoni
2017-07-29 13:09 ` [Buildroot] [PATCH 4/4] binutils: remove support for 2.26 Thomas Petazzoni
2017-07-31 19:27 ` [Buildroot] [PATCH 0/4] Update binutils package Thomas Petazzoni
2017-07-31 19:29 ` Waldemar Brodkorb [this message]
2017-08-01 21:38 ` Thomas Petazzoni
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=20170731192924.GH31395@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.