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. 1dcdebb413c2d6a324b277b8b23d8ae5582a4c91
Date: Sat, 16 Apr 2022 13:24:35 +0000 (GMT)	[thread overview]
Message-ID: <20220416132435.C9F55385803E@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  1dcdebb413c2d6a324b277b8b23d8ae5582a4c91 (commit)
       via  771ba5f8386afe082d41f47d504b405784785ac7 (commit)
      from  adefeb2b20b4bce5575bd550a48cb476e001987f (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 1dcdebb413c2d6a324b277b8b23d8ae5582a4c91
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sat Apr 16 07:24:03 2022 -0600

    frontends: Move www.gnu-pascal.de to https

diff --git a/htdocs/frontends.html b/htdocs/frontends.html
index 748ca182..3aa06bbb 100644
--- a/htdocs/frontends.html
+++ b/htdocs/frontends.html
@@ -29,7 +29,7 @@ are very mature.</p>
 
 <ul>
 
-<li><a href="http://www.gnu-pascal.de/gpc/h-index.html">GNU Pascal Compiler</a> (GPC).</li>
+<li><a href="https://www.gnu-pascal.de/gpc/h-index.html">GNU Pascal Compiler</a> (GPC).</li>
 
 <li><a
 href="https://mercurylang.org/download/gcc-backend.html">Mercury</a>,

commit 771ba5f8386afe082d41f47d504b405784785ac7
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sat Apr 16 07:12:53 2022 -0600

    gcc-12: Fix two markup issues

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 9daf3c51..4f904bfd 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -221,14 +221,14 @@ a work-in-progress.</p>
       <code>exit when</code>. The following expression is therefore
       now valid <code>raise Constraint_Error with "Element is null"
       when Element = null;</code></li>
-    <li>Pattern matching</li>
+    <li>Pattern matching
     <ul>
       <li>The <code>case</code> statement has been extended to cover
         records and arrays as well as finer grained casing on scalar
         types. In the future it is expected to provide more compile
         time guarantees when accessing discriminated fields. Case
         exhaustion is supported for pattern matching. An example would
-        be <code><pre>
+        be <pre>
 type Sign is (Neg, Zero, Pos);
 
 function Multiply (S1, S2 : Sign) return Sign is
@@ -236,7 +236,7 @@ function Multiply (S1, S2 : Sign) return Sign is
      when (Neg, Neg) | (Pos, Pos) =&gt; Pos,
      when (Zero, &lt;&gt;) | (&lt;&gt;, Zero) =&gt; Zero,
      when (Neg, Pos) | (Pos, Neg) =&gt; Neg);
-        </pre></code></li>
+        </pre></li>
     </ul>
     </li>
   </ul>

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

Summary of changes:
 htdocs/frontends.html      | 2 +-
 htdocs/gcc-12/changes.html | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2022-04-16 13:24 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=20220416132435.C9F55385803E@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).