Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* doc/xml/manual/appendix_contributing.xml: Change URLs to use
https.
* doc/html/manual/*: Regenerate.
---
.../doc/html/manual/appendix_contributing.html | 8 ++++----
libstdc++-v3/doc/html/manual/source_code_style.html | 4 ++--
.../doc/xml/manual/appendix_contributing.xml | 12 ++++++------
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
index 0dcafcb98af..ac607fcfad4 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.
--
2.43.0
