From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] wwwdocs: readings: Move www.open-std.org links to https
Date: Mon, 16 Jan 2023 20:28:56 +0100 (CET) [thread overview]
Message-ID: <20230116192915.7C8DF33F27@hamza.pair.com> (raw)
This looks like the largest remaining block of related issues...
Gerald
---
htdocs/readings.html | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/htdocs/readings.html b/htdocs/readings.html
index 5e3db8c2..295cc51f 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -329,39 +329,39 @@ names.
<ul>
- <li><a href="http://www.open-std.org/jtc1/sc22/wg14/">WG14 (C
+ <li><a href="https://www.open-std.org/jtc1/sc22/wg14/">WG14 (C
standards committee)</a></li>
- <li><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n897.pdf">Draft
+ <li><a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/n897.pdf">Draft
C99 Rationale</a></li>
- <li><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/summary.htm">C99
+ <li><a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/summary.htm">C99
Defect Reports</a></li>
<li><a href="http://www.lysator.liu.se/c/rat/title.html">C89
Rationale (HTML)</a></li>
- <li><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/tc1.htm">C89
+ <li><a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/tc1.htm">C89
Technical Corrigendum 1</a></li>
- <li><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/tc2.htm">C89
+ <li><a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/tc2.htm">C89
Technical Corrigendum 2</a></li>
- <li><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/dr.htm">C89
+ <li><a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/dr.htm">C89
Defect Reports</a></li>
</ul></li>
<li>Sequence point rules in C:
<ul>
- <li><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n925.htm">
+ <li><a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/n925.htm">
A formal model of sequence points and related issues by
Clive Feather</a></li>
<li><a href="https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-453.pdf">
C formalised in HOL, thesis by Michael Norrish</a></li>
- <li><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n926.htm">
+ <li><a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/n926.htm">
Sequence points analysis by Raymond Mak</a></li>
- <li><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n927.htm">
+ <li><a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/n927.htm">
Another formalism for sequence points by D. Hugh Redelmeier</a></li>
</ul></li>
@@ -379,7 +379,7 @@ names.
<h3>C++ information</h3>
<ul>
- <li><a href="http://www.open-std.org/jtc1/sc22/wg21/">ISO Committee homepage
+ <li><a href="https://www.open-std.org/jtc1/sc22/wg21/">ISO Committee homepage
(defects list, etc)</a></li>
</ul>
@@ -494,7 +494,7 @@ names.
<li>Ada standards information:
<ul>
- <li><a href="http://www.open-std.org/jtc1/sc22/wg9/">WG9 (Ada
+ <li><a href="https://www.open-std.org/jtc1/sc22/wg9/">WG9 (Ada
standards committee):</a>
<ul>
<li><a href="http://www.ada-auth.org/ais.html">Ada Issues</a></li>
--
2.38.1
reply other threads:[~2023-01-16 19:29 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=20230116192915.7C8DF33F27@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).