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. 85a461714254493fed1ee07a0f1a28c898b023c1
Date: Sat, 29 Oct 2022 15:05:48 +0000 (GMT)	[thread overview]
Message-ID: <20221029150600.3CA1A3858D28@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  85a461714254493fed1ee07a0f1a28c898b023c1 (commit)
      from  b8ed1ae1f8d0def47359f18b36b3973174c048cf (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 85a461714254493fed1ee07a0f1a28c898b023c1
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sat Oct 29 17:05:17 2022 +0200

    readings: Update Go-related links to new site

diff --git a/htdocs/readings.html b/htdocs/readings.html
index f0327e39..01ccd55d 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -553,9 +553,8 @@ names.
 <h3>Go information</h3>
 
 <ul>
-<li><a href="https://golang.org/">General Go information</a></li>
-<li><a href="https://golang.org/ref/spec">Go language
-    specification</a></li>
+<li><a href="https://go.dev/">General Go information</a></li>
+<li><a href="https://go.dev/ref/spec">Go language specification</a></li>
 </ul>
 
 

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

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


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2022-10-29 15:05 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=20221029150600.3CA1A3858D28@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).