From: Olivier Hainque <hainque@adacore.com>
To: Jeff Law <law@redhat.com>
Cc: Olivier Hainque <hainque@adacore.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Nathan Sidwell <nathan@acm.org>,
Jerome Lambourg <lambourg@adacore.com>,
Douglas B Rupp <rupp@adacore.com>
Subject: Re: common grounds for VxWorks 7 support
Date: Mon, 26 Jun 2017 19:17:00 -0000 [thread overview]
Message-ID: <6EA3E3C5-D979-4AD5-827E-90F720A650E0@adacore.com> (raw)
In-Reply-To: <0627e79e-4b28-ab68-60a6-4641553f3e03@redhat.com>
> On Jun 26, 2017, at 18:44 , Jeff Law <law@redhat.com> wrote:
>
>> If OK on principle, I'm not sure who is to approve the tiny config.gcc part.
> I'd think the tiny config.gcc bits would fall under the VxWorks umbrella
> and you can self-approve.
Wonderful :-) Thanks for confirming Jeff!
Olivier
prev parent reply other threads:[~2017-06-26 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 15:38 Olivier Hainque
2017-06-26 15:56 ` Nathan Sidwell
2017-06-26 16:25 ` Olivier Hainque
2017-06-26 16:44 ` Jeff Law
2017-06-26 19:17 ` Olivier Hainque [this message]
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=6EA3E3C5-D979-4AD5-827E-90F720A650E0@adacore.com \
--to=hainque@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=lambourg@adacore.com \
--cc=law@redhat.com \
--cc=nathan@acm.org \
--cc=rupp@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).