From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] The C++11 issue
Date: Sun, 22 Mar 2015 20:22:21 -0300 [thread overview]
Message-ID: <550F4EAD.10205@zacarias.com.ar> (raw)
In-Reply-To: <550D8592.5040300@mind.be>
On 03/21/2015 11:52 AM, Arnout Vandecappelle wrote:
> BTW, now that bfin internal compiler is gone, can we deprecate 4.5?
Yes, i'll send a patch shortly to deprecate it, we've already discussed
this with Thomas on IRC.
Regards.
next prev parent reply other threads:[~2015-03-22 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 9:28 [Buildroot] The C++11 issue Thomas Petazzoni
2015-03-21 14:52 ` Arnout Vandecappelle
2015-03-22 19:00 ` Bernd Kuhls
2015-03-22 23:22 ` Gustavo Zacarias [this message]
2015-03-21 16:37 ` Romain Naour
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=550F4EAD.10205@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 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.