From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] wwwdocs: gcc-4.5: Update link to MPC
Date: Thu, 3 Feb 2022 00:43:12 +0100 (CET) [thread overview]
Message-ID: <20220202234309.B7AA333ED9@hamza.pair.com> (raw)
This is on top of Martin's changes. Pushed.
Gerald
---
htdocs/gcc-4.5/changes.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-4.5/changes.html b/htdocs/gcc-4.5/changes.html
index c141a4d9..5181bae8 100644
--- a/htdocs/gcc-4.5/changes.html
+++ b/htdocs/gcc-4.5/changes.html
@@ -18,7 +18,7 @@
<ul>
<li id="mpccaveat">GCC now requires the <a
- href="http://www.multiprecision.org/mpc/">MPC</a> library in order to
+ href="https://www.multiprecision.org/mpc/">MPC</a> library in order to
build. See the <a
href="https://gcc.gnu.org/install/prerequisites.html">prerequisites
page</a> for version requirements.</li>
--
2.34.1
reply other threads:[~2022-02-02 23: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:
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=20220202234309.B7AA333ED9@hamza.pair.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@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).