From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: "Dominique d'Humi??res" <dominiq@lps.ens.fr>
Cc: fortran@gcc.gnu.org,
Paul Richard Thomas <paul.richard.thomas@gmail.com>,
Thomas Koenig <tkoenig@netcologne.de>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR 65751 Bogus &L in error message
Date: Tue, 17 Nov 2015 14:54:00 -0000 [thread overview]
Message-ID: <20151117145441.GA84279@troutmask.apl.washington.edu> (raw)
In-Reply-To: <D89F5DCA-C307-40DC-881F-D4B788699161@lps.ens.fr>
On Tue, Nov 17, 2015 at 10:53:52AM +0100, Dominique d'Humi??res wrote:
> Is the following patch OK for trunk and 5.3?
OK.
>
> I have used the legalese found in my draft for Fortran 2015.
> Would it be acceptable to replace
> "with the BIND attribute or the SEQUENCE attribute"
> with
> "with the BIND or SEQUENCE attribute"?
In my opinion, yes.
--
Steve
prev parent reply other threads:[~2015-11-17 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 9:53 Dominique d'Humières
2015-11-17 14:54 ` Steve Kargl [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=20151117145441.GA84279@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
--cc=tkoenig@netcologne.de \
/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).