public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry DeLisle <jvdelisle@charter.net>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>,
	Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [gomp4.5] Parsing of most of OpenMP 4.5 clauses
Date: Tue, 10 May 2016 17:51:00 -0000	[thread overview]
Message-ID: <57321FAD.6@charter.net> (raw)
In-Reply-To: <CAGkQGiKC=gEky_N-c-5rTXPnz89d59704_UC1DZAc0mcP0ikgA@mail.gmail.com>

On 05/07/2016 11:42 AM, Paul Richard Thomas wrote:
> Dear Jakub,
> 
> As you might have noticed, I am forced to spend a couple of months out
> from gfortran support in order to move from France back to the UK. I
> am therefore dealing very sporadically with patches. Since we seem to
> have entered a phase where all the other gfortran contributors have
> gone quiet, I suggest that where omp patches are concerned you commit
> when you are satisfied that all is well.
> 
> I have taken a rapid look through your patch and cannot see anything
> to object to. OK by me for trunk.
> 
> Cheers
> 
> Paul
> 

Paul, I concur with your suggestion for omp patches.  I am keeping an eye on
things with Dominique, but some areas we are  weak in expertise.  That being
said, if I don't see anything stupid I will OK non-omp front-end patches
provided they are from people we obviously know are experts.

Jerry

      parent reply	other threads:[~2016-05-10 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-06 19:33 Jakub Jelinek
2016-05-07 18:42 ` Paul Richard Thomas
2016-05-07 18:47   ` Jakub Jelinek
2016-05-10 17:51   ` Jerry DeLisle [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=57321FAD.6@charter.net \
    --to=jvdelisle@charter.net \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=paul.richard.thomas@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).