From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] wwwdocs: readings: Switch sourceforge.net sub-sites to https
Date: Tue, 1 Nov 2022 13:09:50 +0100 (CET) [thread overview]
Message-ID: <20221101120952.60F9933E4A@hamza.pair.com> (raw)
Pushed.
Gerald
---
htdocs/readings.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
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="http://ftp.axis.se/pub/users/hp/pgccfd/">Porting GCC for
Dunces</a> by Hans-Peter Nilsson <<a href="mailto:hans-peter.nilsson@axis.com">hans-peter.nilsson@axis.com</a>>.</li>
-->
- <li><a href="http://cobolforgcc.sourceforge.net/cobol_toc.html">Using,
+ <li><a href="https://cobolforgcc.sourceforge.net/cobol_toc.html">Using,
Maintaining and Enhancing COBOL for the GNU Compiler Collection (GCC)</a>
by Joachim Nadler and Tim Josling
<<a href="mailto:tej@melbpc.org.au">tej@melbpc.org.au</a>>.</li>
@@ -440,12 +440,12 @@ names.
therefore makes it possible to stress the compiler error handling.
</li>
<li>
- <a href="http://flibs.sourceforge.net"><cite>Checking
+ <a href="https://flibs.sourceforge.net"><cite>Checking
properties of the compiler and the run-time environment</cite></a> by
Arjen Markus (source provided).
</li>
<li>
- <a href="http://gdbf95.sourceforge.net/">gdbf95</a> testsuite.
+ <a href="https://gdbf95.sourceforge.net">gdbf95</a> testsuite.
</li>
<li>
Tests of run-time checking capabilities
--
2.38.0
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:
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=20221101120952.60F9933E4A@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).