From: Mike Stump <mikestump@comcast.net>
To: FX <fxcoudert@gmail.com>
Cc: Jack Howarth <howarth.at.gcc@gmail.com>,
Richard Henderson <rth@redhat.com>,
Jakub Jelinek <jakub@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Fortran List <fortran@gcc.gnu.org>
Subject: Re: [patch,libgomp] Make libgomp Fortran modules multilib-aware
Date: Mon, 09 Jan 2017 18:50:00 -0000 [thread overview]
Message-ID: <8475D7BD-DA14-4697-9EB2-8082C6DC5520@comcast.net> (raw)
In-Reply-To: <929E41CA-3ADF-4C09-90D5-CD13660F5E35@gmail.com>
On Jan 9, 2017, at 2:04 AM, FX <fxcoudert@gmail.com> wrote:
>
> Given lack of review of this Fortran-specific patch for libgomp, can a Fortran maintainer approve it please?
Ok.
prev parent reply other threads:[~2017-01-09 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4795FF84-EC6B-448F-991E-AAA8948D5EE4@gmail.com>
[not found] ` <CAJMcOU-k8ni+y05YH6CaxH3KAmHNjSYkXAqs-NYPWaNztK+Xtw@mail.gmail.com>
[not found] ` <93D9F5BF-2BFD-4DC9-957E-EB3CAA41E7D9@gmail.com>
[not found] ` <AD0AE248-C557-4A37-87C5-BFE14DCA4F96@gmail.com>
2016-12-26 11:28 ` FX
2017-01-09 10:04 ` FX
2017-01-09 18:50 ` Mike Stump [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=8475D7BD-DA14-4697-9EB2-8082C6DC5520@comcast.net \
--to=mikestump@comcast.net \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=howarth.at.gcc@gmail.com \
--cc=jakub@redhat.com \
--cc=rth@redhat.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).