public inbox for
help / color / mirror / Atom feed
From: Gerald Pfeifer <>
Subject: gcc-wwwdocs branch master updated. 7d5efd085c2b0ec141b837afb1f79722eaf74376
Date: Sat, 18 Feb 2023 22:31:02 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  7d5efd085c2b0ec141b837afb1f79722eaf74376 (commit)
      from  5614cd60fcf53700d8d3a43c48cb8db31c3b9cdf (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 7d5efd085c2b0ec141b837afb1f79722eaf74376
Author: Gerald Pfeifer <>
Date:   Sat Feb 18 23:30:33 2023 +0100

    gcc-12: Simplify a sentence in the OpenMP section

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
     <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
       available in C and C++ before: <code>declare variant</code> is now
       available, <code>depobj</code>, <code>mutexinoutset</code> and
       <code>iterator</code> can now also be used with the <code>depend</code>


Summary of changes:
 htdocs/gcc-12/changes.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


                 reply	other threads:[~2023-02-18 22:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).