From: Jonathan Wakely Date: Wed, 28 Feb 2024 14:36:28 +0000 (+0000) Subject: libstdc++: Change some URLs in the manual to use https X-Git-Tag: basepoints/gcc-15~921 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=06866bc368f828fa4f3dad25588d038414944c2e;p=thirdparty%2Fgcc.git 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. --- diff --git a/libstdc++-v3/doc/html/manual/appendix_contributing.html b/libstdc++-v3/doc/html/manual/appendix_contributing.html index cd2c1e153d72..24d5a044dd8d 100644 --- a/libstdc++-v3/doc/html/manual/appendix_contributing.html +++ b/libstdc++-v3/doc/html/manual/appendix_contributing.html @@ -10,7 +10,7 @@

Table of Contents

Contributor Checklist
Reading
Assignment
Getting Sources
Submitting Patches
Directory Layout and Source Conventions
Coding Style
Bad Identifiers
By Example
Design Notes

The GNU C++ Library is part of GCC and follows the same development model, so the general rules for - contributing + contributing to GCC apply. Active contributors are assigned maintainership responsibility, and given write access to the source repository. First-time contributors @@ -34,7 +34,7 @@ https://www.open-std.org/jtc1/sc22/wg21

  • Peruse - the GNU + the GNU Coding Standards, and chuckle when you hit the part about “Using Languages Other Than C”.

  • @@ -46,7 +46,7 @@ library-specific information found in Porting and Maintenance.

    • Assignment

    - See the legal prerequisites for all GCC contributions. + See the legal prerequisites for all GCC contributions.

    Historically, the libstdc++ assignment form added the following question: @@ -83,7 +83,7 @@ some recent commits for format and content. The contrib/mklog.py script can be used to generate a ChangeLog template for commit messages. See - Read-write Git access + Read-write Git access for scripts and aliases that are useful here.

  • 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 26b7ea577d56..b0b22683f67c 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
          Standard, which can be referenced in full here:

    -      http://www.gnu.org/prep/standards/standards.html#Formatting
    +      https://www.gnu.org/prep/standards/standards.html#Formatting

          The rest of this is also interesting reading, but skip the "Design
          Advice" part.

          The GCC coding conventions are here, and are also useful:
    -      http://gcc.gnu.org/codingconventions.html
    +      https://gcc.gnu.org/codingconventions.html

          In addition, because it doesn't seem to be stated explicitly anywhere
          else, there is an 80 column source limit.
    diff --git a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml index 0dcafcb98afd..ac607fcfad41 100644 --- a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml +++ b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml @@ -20,7 +20,7 @@ The GNU C++ Library is part of GCC and follows the same development model, so the general rules for - contributing + contributing to GCC apply. Active contributors are assigned maintainership responsibility, and given write access to the source repository. First-time contributors @@ -64,7 +64,7 @@ Peruse - the GNU + the GNU Coding Standards, and chuckle when you hit the part about Using Languages Other Than C. @@ -91,7 +91,7 @@

    Assignment - See the legal prerequisites for all GCC contributions. + See the legal prerequisites for all GCC contributions. @@ -155,7 +155,7 @@ some recent commits for format and content. The contrib/mklog.py script can be used to generate a ChangeLog template for commit messages. See - Read-write Git access + Read-write Git access for scripts and aliases that are useful here. @@ -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: - http://www.gnu.org/prep/standards/standards.html#Formatting + https://www.gnu.org/prep/standards/standards.html#Formatting The rest of this is also interesting reading, but skip the "Design Advice" part. The GCC coding conventions are here, and are also useful: - http://gcc.gnu.org/codingconventions.html + https://gcc.gnu.org/codingconventions.html In addition, because it doesn't seem to be stated explicitly anywhere else, there is an 80 column source limit.