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. 64ae057765cb5500d14502846e4f94540fb0a4b8
Date: Thu, 10 Feb 2022 08:03:51 +0000 (GMT)	[thread overview]
Message-ID: <20220210080351.E426C3858406@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  64ae057765cb5500d14502846e4f94540fb0a4b8 (commit)
      from  a385664808c02ca56f86d76e66227c23db142c68 (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 64ae057765cb5500d14502846e4f94540fb0a4b8
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Thu Feb 10 09:03:29 2022 +0100

    frontends: Adjust the Mercury reference

diff --git a/htdocs/frontends.html b/htdocs/frontends.html
index cd67b089..748ca182 100644
--- a/htdocs/frontends.html
+++ b/htdocs/frontends.html
@@ -32,7 +32,7 @@ are very mature.</p>
 <li><a href="http://www.gnu-pascal.de/gpc/h-index.html">GNU Pascal Compiler</a> (GPC).</li>
 
 <li><a
-href="http://www.mercurylang.org/download/gcc-backend.html">Mercury</a>,
+href="https://mercurylang.org/download/gcc-backend.html">Mercury</a>,
 a declarative logic/functional language. The University of Melbourne Mercury
 compiler is written in Mercury; originally it compiled via C but now it also
 has a back end that generates assembler directly, using the GCC back end.</li>

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2022-02-10  8:03 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=20220210080351.E426C3858406@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).