From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Harald Anlauf <anlauf@gmx.de>
Cc: fortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: fix typo in documentation of intrinsic FLOOR [PR107870]
Date: Sun, 4 Dec 2022 21:09:54 +0000 [thread overview]
Message-ID: <CAGkQGi+0JgrD3Chp8yT0KC=wbkpACv1ijUbf4C=RGOa50mc1KA@mail.gmail.com> (raw)
In-Reply-To: <19b6ebbb-4d42-ba0d-55ba-83fd8cffcbdd@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
Hi Harald,
You will, perhaps, rue having me back when you see the updated finalization
patch :-) This time, I will be breaking it up into digestible chunks!
I'll be posting in about one week.
Regards
Paul
On Sun, 4 Dec 2022 at 19:40, Harald Anlauf <anlauf@gmx.de> wrote:
> Hi Paul,
>
> thanks - and it is good to see that you are back!
>
> Harald
>
> Am 04.12.22 um 12:48 schrieb Paul Richard Thomas via Gcc-patches:
> > Hi Harald,
> >
> > That's good to commit.
> >
> > Thanks for the patch.
> >
> > Paul
> >
> >
> >
> > On Sat, 3 Dec 2022 at 20:40, Harald Anlauf via Fortran <
> fortran@gcc.gnu.org>
> > wrote:
> >
> >> Dear all,
> >>
> >> here's a small documentation fix for the intrinsic FLOOR.
> >> Besides that, I adjusted the description of the optional
> >> KIND argument to Fortran intrinsics to conform to the F2018
> >> standard, which reads "scalar integer constant expression".
> >>
> >> Tested with "make dvi".
> >>
> >> OK for mainline?
> >>
> >> Thanks,
> >> Harald
> >>
> >>
> >
>
>
--
"If you can't explain it simply, you don't understand it well enough" -
Albert Einstein
prev parent reply other threads:[~2022-12-04 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 20:24 Harald Anlauf
2022-12-04 11:48 ` Paul Richard Thomas
2022-12-04 19:40 ` Harald Anlauf
2022-12-04 21:09 ` Paul Richard Thomas [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='CAGkQGi+0JgrD3Chp8yT0KC=wbkpACv1ijUbf4C=RGOa50mc1KA@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
/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).