From: Thomas Koenig <tkoenig@netcologne.de>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
Thomas Koenig via Fortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran, doc] Mention new CONVERT options for POWER
Date: Fri, 29 Apr 2022 20:03:55 +0200 [thread overview]
Message-ID: <2b6a41ed-d50d-8181-fe45-4f26a16f0b35@netcologne.de> (raw)
In-Reply-To: <22C2D776-4F8E-463F-BD21-FB2A90656291@gmail.com>
On 28.04.22 19:17, Bernhard Reutner-Fischer wrote:
> ISTM that this should be s/mod.e/mode./ ?
Yep, fixed as obvious and simple on trunk with
r13-49-g4a8b45e8bc8246bd141dad65f571a3e0cc499c6b .
OK for backport to gcc-12? (This is both extremely safe and
not particularly important :-)
Best regards
Thomas
next prev parent reply other threads:[~2022-04-29 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 20:34 Thomas Koenig
2022-04-28 7:20 ` Richard Biener
2022-04-28 17:17 ` Bernhard Reutner-Fischer
2022-04-29 18:03 ` Thomas Koenig [this message]
2022-04-29 23:26 ` Bernhard Reutner-Fischer
2022-05-02 6:32 ` Richard Biener
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=2b6a41ed-d50d-8181-fe45-4f26a16f0b35@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rep.dot.nop@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).