From: NightStrike <nightstrike@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Tobias Burnus <tobias@codesourcery.com>
Subject: Re: [pushed] wwwdocs: gcc-12: Simplify a sentence in the OpenMP section
Date: Sat, 18 Feb 2023 17:36:40 -0500 [thread overview]
Message-ID: <CAF1jjLs53GZ7rq+7n8Q=qC0TYzTdOuDwDrN8npwSqcRP_ye4cg@mail.gmail.com> (raw)
In-Reply-To: <20230218223206.5458033E77@hamza.pair.com>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
On Sat, Feb 18, 2023, 17:32 Gerald Pfeifer <gerald@pfeifer.com> wrote:
> That was a bit too much in terms of additions things. :-)
>
> Pushed.
>
> Gerald
> ---
> htdocs/gcc-12/changes.html | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
> index 32403579..fd4062e6 100644
> --- a/htdocs/gcc-12/changes.html
> +++ b/htdocs/gcc-12/changes.html
> @@ -153,7 +153,7 @@ You may also want to check out our
> <ul>
> <li>OpenMP 5.0 support has been extended: The <code>close</code> map
> modifier and the <code>affinity</code> clause are now supported.
> - In addition Fortran gained additionally the following features
> which were
> + In addition Fortran gained the following features which were
>
Missing a comma after "in addition" and "features". For the latter, "x that
y" > no comma. "X, which y" > comma. For the former, it's required to
separate the prepositional phrase from the subject.
>
next prev parent reply other threads:[~2023-02-18 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 22:32 Gerald Pfeifer
2023-02-18 22:36 ` NightStrike [this message]
2023-02-19 0:12 ` Gerald Pfeifer
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='CAF1jjLs53GZ7rq+7n8Q=qC0TYzTdOuDwDrN8npwSqcRP_ye4cg@mail.gmail.com' \
--to=nightstrike@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=tobias@codesourcery.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).