https://gcc.gnu.org/g:7b9fa0982f4db0a64aacfe5018708a89f956245a
commit r12-10224-g7b9fa0982f4db0a64aacfe5018708a89f956245a
Author: Jonathan Wakely <jwak...@redhat.com>
Date: Wed Feb 28 14:36:28 2024 +0000
libstdc++: Change some URLs in the manual to use https
libstdc++-v3/ChangeLog:
* doc/xml/manual/appendix_contributing.xml: Change URLs to use
https.
* doc/html/manual/*: Regenerate.
(cherry picked from commit 06866bc368f828fa4f3dad25588d038414944c2e)
Diff:
---
libstdc++-v3/doc/html/manual/appendix_contributing.html | 8 ++++----
libstdc++-v3/doc/html/manual/source_code_style.html | 4 ++--
libstdc++-v3/doc/xml/manual/appendix_contributing.xml | 12 ++++++------
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/libstdc++-v3/doc/html/manual/appendix_contributing.html
b/libstdc++-v3/doc/html/manual/appendix_contributing.html
index 2d04cadd4e8..25d0944e187 100644
--- a/libstdc++-v3/doc/html/manual/appendix_contributing.html
+++ b/libstdc++-v3/doc/html/manual/appendix_contributing.html
@@ -10,7 +10,7 @@
</h1></div></div></div><div class="toc"><p><strong>Table of
Contents</strong></p><dl class="toc"><dt><span class="section"><a
href="appendix_contributing.html#contrib.list">Contributor
Checklist</a></span></dt><dd><dl><dt><span class="section"><a
href="appendix_contributing.html#list.reading">Reading</a></span></dt><dt><span
class="section"><a
href="appendix_contributing.html#list.copyright">Assignment</a></span></dt><dt><span
class="section"><a href="appendix_contributing.html#list.getting">Getting
Sources</a></span></dt><dt><span class="section"><a
href="appendix_contributing.html#list.patches">Submitting
Patches</a></span></dt></dl></dd><dt><span class="section"><a
href="source_organization.html">Directory Layout and Source
Conventions</a></span></dt><dt><span class="section"><a
href="source_code_style.html">Coding Style</a></span></dt><dd><dl><dt><span
class="section"><a
href="source_code_style.html#coding_style.bad_identifiers">Bad
Identifiers</a></span></dt><dt><span class="se
ction"><a href="source_code_style.html#coding_style.example">By
Example</a></span></dt></dl></dd><dt><span class="section"><a
href="source_design_notes.html">Design Notes</a></span></dt></dl></div><p>
The GNU C++ Library is part of GCC and follows the same development model,
so the general rules for
- <a class="link" href="http://gcc.gnu.org/contribute.html";
target="_top">contributing
+ <a class="link" href="https://gcc.gnu.org/contribute.html";
target="_top">contributing
to GCC</a> apply. Active
contributors are assigned maintainership responsibility, and given
write access to the source repository. First-time contributors
@@ -34,7 +34,7 @@
<a class="link" href="http://www.open-std.org/jtc1/sc22/wg21/";
target="_top">http://www.open-std.org/jtc1/sc22/wg21</a>
</p></li><li class="listitem"><p>
Peruse
- the <a class="link" href="http://www.gnu.org/prep/standards/";
target="_top">GNU
+ the <a class="link" href="https://www.gnu.org/prep/standards/";
target="_top">GNU
Coding Standards</a>, and chuckle when you hit the part
about <span class="quote">“<span class="quote">Using Languages Other
Than C</span>”</span>.
</p></li><li class="listitem"><p>
@@ -46,7 +46,7 @@
library-specific information found in
<a class="link" href="appendix_porting.html" title="Appendix B.
Porting and Maintenance">Porting and Maintenance</a>.
</p></li></ul></div></div><div class="section"><div
class="titlepage"><div><div><h3 class="title"><a
id="list.copyright"></a>Assignment</h3></div></div></div><p>
- See the <a class="link" href="http://gcc.gnu.org/contribute.html#legal";
target="_top">legal prerequisites</a> for all GCC contributions.
+ See the <a class="link" href="https://gcc.gnu.org/contribute.html#legal";
target="_top">legal prerequisites</a> for all GCC contributions.
</p><p>
Historically, the libstdc++ assignment form added the following
question:
@@ -83,7 +83,7 @@
some recent commits for format and content. The
<code class="filename">contrib/mklog.py</code> script can be used to
generate a ChangeLog template for commit messages. See
- <a class="link" href="http://gcc.gnu.org/gitwrite.html";
target="_top">Read-write Git access</a>
+ <a class="link" href="https://gcc.gnu.org/gitwrite.html";
target="_top">Read-write Git access</a>
for scripts and aliases that are useful here.
</p></li><li class="listitem"><p>
A testsuite submission or sample program that will
diff --git a/libstdc++-v3/doc/html/manual/source_code_style.html
b/libstdc++-v3/doc/html/manual/source_code_style.html
index 24e0d693127..1c0d00a5df8 100644
--- a/libstdc++-v3/doc/html/manual/source_code_style.html
+++ b/libstdc++-v3/doc/html/manual/source_code_style.html
@@ -197,13 +197,13 @@
it is intended to precede the recommendations of the GNU Coding<br />
Standard, which can be referenced in full here:<br />
<br />
- <a class="link"
href="http://www.gnu.org/prep/standards/standards.html#Formatting";
target="_top">http://www.gnu.org/prep/standards/standards.html#Formatting</a><br
/>
+ <a class="link"
href="https://www.gnu.org/prep/standards/standards.html#Formatting";
target="_top">https://www.gnu.org/prep/standards/standards.html#Formatting</a><br
/>
<br />
The rest of this is also interesting reading, but skip the "Design<br />
Advice" part.<br />
<br />
The GCC coding conventions are here, and are also useful:<br />
- <a class="link" href="http://gcc.gnu.org/codingconventions.html";
target="_top">http://gcc.gnu.org/codingconventions.html</a><br />
+ <a class="link" href="https://gcc.gnu.org/codingconventions.html";
target="_top">https://gcc.gnu.org/codingconventions.html</a><br />
<br />
In addition, because it doesn't seem to be stated explicitly anywhere<br
/>
else, there is an 80 column source limit.<br />
diff --git a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
index 074baf0fb4d..2509330d807 100644
--- a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
+++ b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
@@ -20,7 +20,7 @@
<para>
The GNU C++ Library is part of GCC and follows the same development model,
so the general rules for
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/contribute.html";>contributing
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/contribute.html";>contributing
to GCC</link> apply. Active
contributors are assigned maintainership responsibility, and given
write access to the source repository. First-time contributors
@@ -64,7 +64,7 @@
<listitem>
<para>
Peruse
- the <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://www.gnu.org/prep/standards/";>GNU
+ the <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://www.gnu.org/prep/standards/";>GNU
Coding Standards</link>, and chuckle when you hit the part
about <quote>Using Languages Other Than C</quote>.
</para>
@@ -91,7 +91,7 @@
<section xml:id="list.copyright"><info><title>Assignment</title></info>
<para>
- See the <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/contribute.html#legal";>legal
prerequisites</link> for all GCC contributions.
+ See the <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/contribute.html#legal";>legal
prerequisites</link> for all GCC contributions.
</para>
<para>
@@ -155,7 +155,7 @@
some recent commits for format and content. The
<filename>contrib/mklog.py</filename> script can be used to
generate a ChangeLog template for commit messages. See
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/gitwrite.html";>Read-write Git access</link>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/gitwrite.html";>Read-write Git access</link>
for scripts and aliases that are useful here.
</para>
</listitem>
@@ -618,13 +618,13 @@ indicate a place that may require attention for
multi-thread safety.
it is intended to precede the recommendations of the GNU Coding
Standard, which can be referenced in full here:
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://www.gnu.org/prep/standards/standards.html#Formatting";>http://www.gnu.org/prep/standards/standards.html#Formatting</link>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://www.gnu.org/prep/standards/standards.html#Formatting";>https://www.gnu.org/prep/standards/standards.html#Formatting</link>
The rest of this is also interesting reading, but skip the "Design
Advice" part.
The GCC coding conventions are here, and are also useful:
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/codingconventions.html";>http://gcc.gnu.org/codingconventions.html</link>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/codingconventions.html";>https://gcc.gnu.org/codingconventions.html</link>
In addition, because it doesn't seem to be stated explicitly anywhere
else, there is an 80 column source limit.
