From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: [pushed] libstdc++: Move gcc.gnu.org links to https
Date: Sun, 2 Jun 2024 12:36:04 +0200 (CEST) [thread overview]
Message-ID: <20240602103608.051D233E79@hamza.pair.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=X-UNKNOWN, Size: 4395 bytes --]
It looks like there are more links needing similar changes; one step at a
time...
Gerald
libstdc++-v3:
* doc/xml/api.xml: Move gcc.gnu.org links to https.
* doc/html/api.html: Regenerate.
---
libstdc++-v3/doc/html/api.html | 8 ++++----
libstdc++-v3/doc/xml/api.xml | 6 +++---
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/libstdc++-v3/doc/html/api.html b/libstdc++-v3/doc/html/api.html
index fc27b5f98ae..b494d91f9af 100644
--- a/libstdc++-v3/doc/html/api.html
+++ b/libstdc++-v3/doc/html/api.html
@@ -21,9 +21,9 @@
particular include file, looking at inheritance diagrams, etc.
</p><p>
The API documentation, rendered into HTML, can be viewed online
- <a class="link" href="http://gcc.gnu.org/onlinedocs/" target="_top">for each GCC release</a>
+ <a class="link" href="https://gcc.gnu.org/onlinedocs/" target="_top">for each GCC release</a>
and
- <a class="link" href="http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/index.html" target="_top">
+ <a class="link" href="https://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/index.html" target="_top">
for the main development tree
</a>
(see the date on the first page).
@@ -32,10 +32,10 @@
gcc.gnu.org site in a directory located at
<code class="literal"><URL:https://gcc.gnu.org/pub/gcc/libstdc++/doxygen/></code>.
You will almost certainly need to use one of the
- <a class="link" href="http://gcc.gnu.org/mirrors.html" target="_top">mirror sites</a> to download
+ <a class="link" href="https://gcc.gnu.org/mirrors.html" target="_top">mirror sites</a> to download
the tarball. After unpacking, simply load libstdc++-html-*/index.html
into a browser.
</p><p>
In addition, a rendered set of man pages are available in the same
location specified above. Start with C++Intro(3).
-</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bk02.html">Prev</a>??</td><td width="20%" align="center"><a accesskey="u" href="bk02.html">Up</a></td><td width="40%" align="right">??<a accesskey="n" href="bk03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">??</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">??</td></tr></table></div></body></html>
\ No newline at end of file
+</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bk02.html">Prev</a>??</td><td width="20%" align="center"><a accesskey="u" href="bk02.html">Up</a></td><td width="40%" align="right">??<a accesskey="n" href="bk03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">??</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">??</td></tr></table></div></body></html>
diff --git a/libstdc++-v3/doc/xml/api.xml b/libstdc++-v3/doc/xml/api.xml
index 1b011aa2e23..9aee3484e27 100644
--- a/libstdc++-v3/doc/xml/api.xml
+++ b/libstdc++-v3/doc/xml/api.xml
@@ -41,9 +41,9 @@
<para>
The API documentation, rendered into HTML, can be viewed online
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/onlinedocs/">for each GCC release</link>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/onlinedocs/">for each GCC release</link>
and
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/index.html">
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/index.html">
for the main development tree
</link>
(see the date on the first page).
@@ -54,7 +54,7 @@
gcc.gnu.org site in a directory located at
<literal><URL:https://gcc.gnu.org/pub/gcc/libstdc++/doxygen/></literal>.
You will almost certainly need to use one of the
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/mirrors.html">mirror sites</link> to download
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/mirrors.html">mirror sites</link> to download
the tarball. After unpacking, simply load libstdc++-html-*/index.html
into a browser.
</para>
--
2.45.1
reply other threads:[~2024-06-02 10:36 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=20240602103608.051D233E79@hamza.pair.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).