public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-6130] libstdc++: Switch two links to www.open-std.org to https
Date: Sat, 18 Feb 2023 09:59:56 +0000 (GMT)	[thread overview]
Message-ID: <20230218095956.296CF3858D38@sourceware.org> (raw)

https://gcc.gnu.org/g:3e558fb7f3c8e7f736b23710d94f4226f4df38b8

commit r13-6130-g3e558fb7f3c8e7f736b23710d94f4226f4df38b8
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sat Feb 18 10:59:11 2023 +0100

    libstdc++: Switch two links to www.open-std.org to https
    
    libstdc++-v3/ChangeLog:
    
            * doc/xml/faq.xml: Switch two links to www.open-std.org to https.
            * doc/html/faq.html: Regenerate.

Diff:
---
 libstdc++-v3/doc/html/faq.html | 4 ++--
 libstdc++-v3/doc/xml/faq.xml   | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html
index f49b84c4c33..965aa91d031 100644
--- a/libstdc++-v3/doc/html/faq.html
+++ b/libstdc++-v3/doc/html/faq.html
@@ -541,7 +541,7 @@
     For those people who are not part of the ISO Library Group
     (i.e., nearly all of us needing to read this page in the first
     place), a public list of the library defects is occasionally
-    published on <a class="link" href="http://www.open-std.org/jtc1/sc22/wg21/" target="_top">the WG21
+    published on <a class="link" href="https://www.open-std.org/jtc1/sc22/wg21/" target="_top">the WG21
     website</a>.
     Many of these issues have resulted in
     <a class="link" href="manual/bugs.html#manual.intro.status.bugs.iso" title="Standard Bugs">code changes in libstdc++</a>.
@@ -825,7 +825,7 @@
     Yes.
     </p><p>
     The C++ Standard Library
-    <a class="link" href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf" target="_top">
+    <a class="link" href="https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf" target="_top">
     Technical Report 1</a> added many new features to the library.
     </p><p>
     The implementation status of TR1 in libstdc++ can be tracked
diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml
index 9ae4966ecea..b38091acdc8 100644
--- a/libstdc++-v3/doc/xml/faq.xml
+++ b/libstdc++-v3/doc/xml/faq.xml
@@ -754,7 +754,7 @@
     (i.e., nearly all of us needing to read this page in the first
     place), a public list of the library defects is occasionally
     published on <link xmlns:xlink="http://www.w3.org/1999/xlink"
-    xlink:href="http://www.open-std.org/jtc1/sc22/wg21/">the WG21
+    xlink:href="https://www.open-std.org/jtc1/sc22/wg21/">the WG21
     website</link>.
     Many of these issues have resulted in
     <link linkend="manual.intro.status.bugs.iso">code changes in libstdc++</link>.
@@ -1181,7 +1181,7 @@
     </para>
     <para>
     The C++ Standard Library
-    <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">
+    <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">
     Technical Report 1</link> added many new features to the library.
     </para>
     <para>

                 reply	other threads:[~2023-02-18  9:59 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=20230218095956.296CF3858D38@sourceware.org \
    --to=gerald@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).