public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 11ed08ab4b85f183da5af7c0707bacb589980842
Date: Mon, 20 Feb 2023 09:22:53 +0000 (GMT)	[thread overview]
Message-ID: <20230220092254.152243858D38@sourceware.org> (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  11ed08ab4b85f183da5af7c0707bacb589980842 (commit)
       via  6b8efccd68c53c09e88461cb435c227004a73fba (commit)
      from  7d5efd085c2b0ec141b837afb1f79722eaf74376 (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 11ed08ab4b85f183da5af7c0707bacb589980842
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Mon Feb 20 10:17:04 2023 +0100

    index: Remove link to Nick's blog
    
    Nick has not been able to update his blog for a while and confirmed
    we should remove this link.

diff --git a/htdocs/index.html b/htdocs/index.html
index 80730c06..3d0f8700 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -89,7 +89,6 @@ mission statement</a>.</p>
 
 <div>
 <a href="https://gcc.gnu.org/news.html">Older news</a> |
-<a href="https://developers.redhat.com/author/nick-clifton">Nick's Blog</a> |
 <span class="smaller">
 More news? Let gerald@pfeifer.com know!
 </span>

commit 6b8efccd68c53c09e88461cb435c227004a73fba
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sun Feb 19 20:09:06 2023 +0100

    *: Add a comma after "In addition" when used as transition
    
    On the way reduce one use and simplify a sentence.

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index fd4062e6..c47d3285 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 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>
@@ -170,7 +170,7 @@ You may also want to check out our
       <code>align</code> and <code>allocator</code> modifiers to the
       <code>allocate</code> clause and the <code>atomic</code> extensions are
       now available. The <code>OMP_PLACE</code> environment variable supports
-      the OpenMP 5.1 features. In addition the <code>OMP_NUM_TEAMS</code> and
+      the OpenMP 5.1 features. In addition, the <code>OMP_NUM_TEAMS</code> and
       <code>OMP_TEAMS_THREAD_LIMIT</code> environment variables and their
       associated API routines are now supported as well as the memory-allocation
       routines added for Fortran and extended for C/C++ in OpenMP 5.1. In
diff --git a/htdocs/gcc-3.0/libgcc.html b/htdocs/gcc-3.0/libgcc.html
index d98f9b71..6143db0c 100644
--- a/htdocs/gcc-3.0/libgcc.html
+++ b/htdocs/gcc-3.0/libgcc.html
@@ -12,7 +12,7 @@
 
 <p>This page provides a summary of discussions about the pros and cons
 of distributing <code>libgcc</code> as a shared library, as well as a
-static library.  In addition this page details the plans regarding
+static library.  In addition, it details the plans regarding
 <code>libgcc</code> for the GCC 3.0 release.</p>
 
 <h2>Issues</h2>
diff --git a/htdocs/gcc-5/changes.html b/htdocs/gcc-5/changes.html
index 201a039f..6952f866 100644
--- a/htdocs/gcc-5/changes.html
+++ b/htdocs/gcc-5/changes.html
@@ -1001,7 +1001,7 @@ are not listed here).</p>
 	and built-in support. It is enabled through option <code>-mmwaitx</code>.
 	The instructions <code>monitorx</code> and <code>mwaitx</code>
 	implement the same functionality as the old <code>monitor</code>
-	and <code>mwait</code> instructions. In addition <code>mwaitx</code>
+	and <code>mwait</code> instructions. In addition, <code>mwaitx</code>
 	adds a configurable timer. The timer value is received as third
 	argument and stored in register <code>%ebx</code>.</li>
   </ul>
diff --git a/htdocs/gcc-6/changes.html b/htdocs/gcc-6/changes.html
index b400dd9c..0c7d2582 100644
--- a/htdocs/gcc-6/changes.html
+++ b/htdocs/gcc-6/changes.html
@@ -566,7 +566,7 @@ within strings:
        and built-in support. It is enabled through option <code>-mmwaitx</code>.
        The instructions <code>monitorx</code> and <code>mwaitx</code>
        implement the same functionality as the old <code>monitor</code>
-       and <code>mwait</code> instructions. In addition <code>mwaitx</code>
+       and <code>mwait</code> instructions. In addition, <code>mwaitx</code>
        adds a configurable timer. The timer value is received as third
        argument and stored in register <code>%ebx</code>.
      </li>
diff --git a/htdocs/git.html b/htdocs/git.html
index f71b451f..2543c237 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -20,8 +20,8 @@
 large.  That way you can pick up any version (including releases) of
 GCC that is in our repository.</p>
 
-<p>In addition you
-can <a href="https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git">browse our
+<p>In addition, you can
+<a href="https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git">browse our
 Git history online</a>.</p>
 
 <p>(Our <a href="about.html#git">web pages are managed via Git in a
diff --git a/htdocs/spam.html b/htdocs/spam.html
index 349e70c7..43040100 100644
--- a/htdocs/spam.html
+++ b/htdocs/spam.html
@@ -45,8 +45,7 @@ avoid creating unnecessary traffic:</p>
      harvested.</p></li>
 </ul>
 
-<p>In addition may want to check out
-<a href="https://www.abuse.net">www.abuse.net</a>.</p>
+<p>Also check out <a href="https://www.abuse.net">www.abuse.net</a>.</p>
 
 </body>
 </html>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-12/changes.html | 4 ++--
 htdocs/gcc-3.0/libgcc.html | 2 +-
 htdocs/gcc-5/changes.html  | 2 +-
 htdocs/gcc-6/changes.html  | 2 +-
 htdocs/git.html            | 4 ++--
 htdocs/index.html          | 1 -
 htdocs/spam.html           | 3 +--
 7 files changed, 8 insertions(+), 10 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-02-20  9:22 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:
  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=20230220092254.152243858D38@sourceware.org \
    --to=gerald@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).