public inbox for
help / color / mirror / Atom feed
From: Gerald Pfeifer <>
Subject: gcc-wwwdocs branch master updated. 67c72bb30309882ce465519e97fb14592d18ff2c
Date: Thu, 14 Apr 2022 04:43:33 +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  67c72bb30309882ce465519e97fb14592d18ff2c (commit)
      from  635acaea5c578425fe10e1b7b12d9b193329333d (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 67c72bb30309882ce465519e97fb14592d18ff2c
Author: Gerald Pfeifer <>
Date:   Wed Apr 13 22:43:05 2022 -0600

    gcc-12: Properly escape < and >.

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index bd9e5122..057d1274 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -205,10 +205,10 @@ a work-in-progress.</p>
     <li>Fixed lower bound for unconstrained arrays.
-      <li><code>type Matrix is array (Natural range 0 .. <>, Natural
-        range 0 .. <>) of Integer;</code> is now valid.</li>
+      <li><code>type Matrix is array (Natural range 0 .. &lt;&gt;,
+	Natural range 0 .. &lt;&gt;) of Integer;</code> is now valid.</li>
       <li>Subtypes can also specify a lower bound: <code>subtype
-        String_1 is String (1 .. <>);</code>. Boundaries from slices
+        String_1 is String (1 .. &lt;&gt;);</code>. Boundaries from slices
         will "slide" to the correct lower bound of the subtype.</li>


Summary of changes:
 htdocs/gcc-12/changes.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)


                 reply	other threads:[~2022-04-14  4:43 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).