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. 254fd33e73494704e453d4cbf634f02f19da6dee
Date: Sat,  1 Jun 2024 09:59:31 +0000 (GMT)	[thread overview]
Message-ID: <20240601095931.9474B388212B@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  254fd33e73494704e453d4cbf634f02f19da6dee (commit)
      from  614b76b185be56e74b607a92b49b359be5949565 (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 254fd33e73494704e453d4cbf634f02f19da6dee
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sat Jun 1 11:59:12 2024 +0200

    news: golang.org has become go.dev

diff --git a/htdocs/news.html b/htdocs/news.html
index b7a6f479..c319e250 100644
--- a/htdocs/news.html
+++ b/htdocs/news.html
@@ -582,7 +582,7 @@ We are currently accepting student applications.</dd>
 
 <dt>December 2, 2010</dt>
 <dd><a href="gcc-4.6/changes.html#go">GCC 4.6</a> will support
-  the <a href="https://golang.org/">Go programming language</a>.  The
+  the <a href="https://go.dev">Go programming language</a>.  The
   new front end was contributed by Ian Lance Taylor at Google.</dd>
 
 <dt>November 16, 2010</dt>

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

Summary of changes:
 htdocs/news.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2024-06-01  9:59 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=20240601095931.9474B388212B@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).