From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,
Joel Brobecker <brobecker@adacore.com>,
"gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Go C++ only
Date: Fri, 02 Sep 2016 15:34:00 -0000 [thread overview]
Message-ID: <87eg521fk4.fsf@redhat.com> (raw)
In-Reply-To: <3d16afa1-fba3-4543-4232-d6c952ea4556@redhat.com> (Pedro Alves's message of "Fri, 2 Sep 2016 11:15:07 +0100")
On Friday, September 02 2016, Pedro Alves wrote:
> On 09/02/2016 11:01 AM, Yao Qi wrote:
>> On Thu, Sep 1, 2016 at 7:17 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>>>
>>> I don't have a strong opinion, but can we perhaps try a compromise
>>> where we would be using C++ features only in new units (unlikely to be
>>> backported)? Even though the backporting rate is indeed probably low,
>>> it would still be nice to make it as easy as possible. Or is this
>>> not really a practical suggestion?
>>>
>>
>> I agree. If we think the patch is likely to be backported, such as bug fix,
>> C++ feature is not allowed in the patch.
>
> Agreed.
>
> Sergio, can you switch the buildbot builder that is catching C
> build regressions to test the 7.12 branch instead of master?
Hm, I can try, yes. I'll let you know if it works.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2016-09-02 15:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 17:32 Pedro Alves
2016-09-01 17:48 ` Dmitry Samersoff
2016-09-01 18:07 ` Simon Marchi
2016-09-01 18:22 ` Pedro Alves
2016-09-01 18:33 ` Simon Marchi
2016-09-01 18:48 ` Pedro Alves
2016-09-01 18:56 ` Pedro Alves
2016-09-01 18:36 ` Andrew Pinski
2016-09-01 19:01 ` Eli Zaretskii
2016-09-01 19:07 ` Pedro Alves
2016-09-01 18:17 ` Joel Brobecker
2016-09-02 10:01 ` Yao Qi
2016-09-02 10:15 ` Pedro Alves
2016-09-02 15:34 ` Sergio Durigan Junior [this message]
2016-09-02 20:10 ` Sergio Durigan Junior
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=87eg521fk4.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.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