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 r11-6335] libstdc++: Convert three doxygen.nl links to https
Date: Fri, 25 Dec 2020 14:23:01 +0000 (GMT)	[thread overview]
Message-ID: <20201225142301.CA3153850425@sourceware.org> (raw)

https://gcc.gnu.org/g:4ee8e5949a9b43c05c17667dd26852f5e9d5b98b

commit r11-6335-g4ee8e5949a9b43c05c17667dd26852f5e9d5b98b
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Fri Dec 25 15:20:43 2020 +0100

    libstdc++: Convert three doxygen.nl links to https
    
    libstdc++-v3:
    2020-12-25  Gerald Pfeifer  <gerald@pfeifer.com>
    
            * doc/xml/manual/documentation_hacking.xml: Convert three links
            to doxygen.nl to https.
            * doc/html/manual/documentation_hacking.html: Regenerate.

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

diff --git a/libstdc++-v3/doc/html/manual/documentation_hacking.html b/libstdc++-v3/doc/html/manual/documentation_hacking.html
index f6f32fbda63..c978d5f3d1f 100644
--- a/libstdc++-v3/doc/html/manual/documentation_hacking.html
+++ b/libstdc++-v3/doc/html/manual/documentation_hacking.html
@@ -114,7 +114,7 @@
       <span class="emphasis"><em>ps</em></span>, and <span class="emphasis"><em>dvi</em></span>.
     </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="doc.doxygen"></a>Doxygen</h3></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="doxygen.prereq"></a>Prerequisites</h4></div></div></div><div class="table"><a id="table.doxygen_prereq"></a><p class="title"><strong>Table B.1. Doxygen Prerequisites</strong></p><div class="table-contents"><table class="table" summary="Doxygen Prerequisites" border="1"><colgroup><col align="center" class="c1" /><col align="center" class="c2" /><col align="center" class="c3" /></colgroup><thead><tr><th align="center">Tool</th><th align="center">Version</th><th align="center">Required By</th></tr></thead><tbody><tr><td align="center">coreutils</td><td align="center">8.5</td><td align="center">all</td></tr><tr><td align="center">bash</td><td align="center">4.1</td><td align="center">all</td></tr><tr><td align="center">doxygen</td><td align="center">1.7.6.1</td><td align="center">all</td></tr><tr><td align="center">graphviz</td><td align="center">2.26</td><td align="center">graphical hierarchies</td></tr><tr><td align="center">pdflatex</td><td align="center">2007-59</td><td align="center">pdf output</td></tr></tbody></table></div></div><br class="table-break" /><p>
 	Prerequisite tools are Bash 2.0 or later,
-	<a class="link" href="http://www.doxygen.nl" target="_top">Doxygen</a>, and
+	<a class="link" href="https://www.doxygen.nl" target="_top">Doxygen</a>, and
 	the <a class="link" href="http://www.gnu.org/software/coreutils/" target="_top">GNU
 	coreutils</a>. (GNU versions of find, xargs, and possibly
 	sed and grep are used, just because the GNU versions make
@@ -232,7 +232,7 @@
       </p><p>
 	Adding Doxygen markup to a file (informally called
 	<span class="quote">“<span class="quote">doxygenating</span>”</span>) is very simple. See the
-	<a class="link" href="http://www.doxygen.nl/download.html#latestman" target="_top">Doxygen
+	<a class="link" href="https://www.doxygen.nl/download.html#latestman" target="_top">Doxygen
          manual</a> for details.
 	We try to use a very-recent version of Doxygen.
       </p><p>
@@ -245,7 +245,7 @@
 	these member functions.
       </p><p>
 	Some commentary to accompany
-	the first list in the <a class="link" href="http://www.doxygen.nl/manual/docblocks.html" target="_top">Special
+	the first list in the <a class="link" href="https://www.doxygen.nl/manual/docblocks.html" target="_top">Special
 	Documentation Blocks</a> section of the Doxygen manual:
       </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>For longer comments, use the Javadoc style...</p></li><li class="listitem"><p>
 	    ...not the Qt style. The intermediate *'s are preferred.
diff --git a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
index 723120808d7..03bf1f184d4 100644
--- a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
+++ b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
@@ -261,7 +261,7 @@
 
       <para>
 	Prerequisite tools are Bash 2.0 or later,
-	<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.doxygen.nl">Doxygen</link>, and
+	<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://www.doxygen.nl">Doxygen</link>, and
 	the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.gnu.org/software/coreutils/">GNU
 	coreutils</link>. (GNU versions of find, xargs, and possibly
 	sed and grep are used, just because the GNU versions make
@@ -447,7 +447,7 @@
 	Adding Doxygen markup to a file (informally called
 	<quote>doxygenating</quote>) is very simple. See the
 	<link xmlns:xlink="http://www.w3.org/1999/xlink"
-         xlink:href="http://www.doxygen.nl/download.html#latestman">Doxygen
+         xlink:href="https://www.doxygen.nl/download.html#latestman">Doxygen
          manual</link> for details.
 	We try to use a very-recent version of Doxygen.
       </para>
@@ -465,7 +465,7 @@
       <para>
 	Some commentary to accompany
 	the first list in the <link xmlns:xlink="http://www.w3.org/1999/xlink"
-        xlink:href="http://www.doxygen.nl/manual/docblocks.html">Special
+        xlink:href="https://www.doxygen.nl/manual/docblocks.html">Special
 	Documentation Blocks</link> section of the Doxygen manual:
       </para>


                 reply	other threads:[~2020-12-25 14:23 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=20201225142301.CA3153850425@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).