From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc: bump 6.x series to 6.2.0
Date: Tue, 23 Aug 2016 00:14:44 +0200 [thread overview]
Message-ID: <20160823001444.6543d2e0@free-electrons.com> (raw)
In-Reply-To: <87twecmps7.fsf@dell.be.48ers.dk>
Hello,
On Mon, 22 Aug 2016 23:56:08 +0200, Peter Korsgaard wrote:
> > Since it has the Blackfin patches, Gustavo's patch is against master.
>
> Yeah. Do we want it for 2016.08? It is strictly seen a bugfix release,
> but it's a scary package to bump this close to the release.
Agreed. I'd rather this see merged in next.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-22 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 20:02 [Buildroot] [PATCH] gcc: bump 6.x series to 6.2.0 Gustavo Zacarias
2016-08-22 21:15 ` Peter Korsgaard
2016-08-22 21:52 ` Thomas Petazzoni
2016-08-22 21:56 ` Peter Korsgaard
2016-08-22 22:14 ` Thomas Petazzoni [this message]
2016-08-23 10:41 ` Gustavo Zacarias
2016-08-26 14:15 ` Thomas Petazzoni
2016-08-26 14:17 ` Gustavo Zacarias
-- strict thread matches above, loose matches on Subject: below --
2016-09-06 1:12 Gustavo Zacarias
2016-09-07 8:33 ` 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=20160823001444.6543d2e0@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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