public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [pushed] wwwdocs: gcc-5: Adjust www.open-std.org links to https
Date: Sat, 21 Jan 2023 18:33:11 +0100 (CET)	[thread overview]
Message-ID: <20230121173312.6E2FE33E62@hamza.pair.com> (raw)

Business as usual.

Gerald
---
 htdocs/gcc-5/changes.html    | 2 +-
 htdocs/gcc-5/porting_to.html | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/htdocs/gcc-5/changes.html b/htdocs/gcc-5/changes.html
index f6742fb0..893e35de 100644
--- a/htdocs/gcc-5/changes.html
+++ b/htdocs/gcc-5/changes.html
@@ -417,7 +417,7 @@ void operator delete[] wwwdocs: (void *, std::size_t) noexcept;</pre></blockquote>
       These warnings can be used at compile time, but they are more
       useful in combination with link-time optimization.</li>
 <li>G++ no longer supports
-  <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3639.html">N3639</a>
+  <a href="https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3639.html">N3639</a>
   variable length arrays, as they were removed from the C++14 working paper
   prior to ratification.  GNU VLAs are still supported, so VLA support is
   now the same in C++14 mode as in C++98 and C++11 modes.</li>
diff --git a/htdocs/gcc-5/porting_to.html b/htdocs/gcc-5/porting_to.html
index b8942aa8..f2a831c4 100644
--- a/htdocs/gcc-5/porting_to.html
+++ b/htdocs/gcc-5/porting_to.html
@@ -380,7 +380,7 @@ For instance:</p>
 
 <p>Converting <code>std::nullptr_t</code> to <code>bool</code> in C++11
 mode now requires direct-initialization.  This has been changed in
-<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1423">DR 1423</a>.</p>
+<a href="https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1423">DR 1423</a>.</p>
 
 <p>As a consequence, the following is invalid:</p>
 
@@ -400,7 +400,7 @@ converting <code>nullptr</code> to <code>bool</code>.
 <h3 id="dr1579">Return by converting move constructor</h3>
 
 <p>GCC 5 implements
-<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1579">DR 1579</a>
+<a href="https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1579">DR 1579</a>
 which means that when compiling a function like:</p>
 
 <pre><code>
-- 
2.39.0

                 reply	other threads:[~2023-01-21 17:33 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=20230121173312.6E2FE33E62@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).