public inbox for
help / color / mirror / Atom feed
From: Gerald Pfeifer <>
Subject: gcc-wwwdocs branch master updated. 5614c9b1f0835f8d27c289a2d501473af512872f
Date: Tue,  1 Nov 2022 12:09:35 +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  5614c9b1f0835f8d27c289a2d501473af512872f (commit)
      from  06e7db17fa454b20c5451144983b76289fd15a3f (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 5614c9b1f0835f8d27c289a2d501473af512872f
Author: Gerald Pfeifer <>
Date:   Tue Nov 1 13:09:13 2022 +0100

    readings: Switch sub-sites to https

diff --git a/htdocs/readings.html b/htdocs/readings.html
index 5622bcc3..df89bc9c 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -34,7 +34,7 @@
   <li><a href="">Porting GCC for
   Dunces</a> by Hans-Peter Nilsson &lt;<a href=""></a>&gt;.</li>
-  <li><a href="">Using,
+  <li><a href="">Using,
   Maintaining and Enhancing COBOL for the GNU Compiler Collection (GCC)</a>
   by Joachim Nadler and Tim Josling
   &lt;<a href=""></a>&gt;.</li>
@@ -440,12 +440,12 @@ names.
         therefore makes it possible to stress the compiler error handling.
-        <a href=""><cite>Checking
+        <a href=""><cite>Checking
         properties of the compiler and the run-time environment</cite></a> by
         Arjen Markus (source provided).
-        <a href="">gdbf95</a> testsuite.
+        <a href="">gdbf95</a> testsuite.
         Tests of run-time checking capabilities


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


                 reply	other threads:[~2022-11-01 12:09 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).