public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] wwwdocs: gcc-4.9: Adjust www.open-std.org links to https
Date: Thu, 19 Jan 2023 15:48:39 +0100 (CET)	[thread overview]
Message-ID: <20230119144841.1B7E233E8E@hamza.pair.com> (raw)

Pushed.

Gerald
---
 htdocs/gcc-4.9/changes.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/htdocs/gcc-4.9/changes.html b/htdocs/gcc-4.9/changes.html
index 274bd814..9090c0ea 100644
--- a/htdocs/gcc-4.9/changes.html
+++ b/htdocs/gcc-4.9/changes.html
@@ -222,7 +222,7 @@
   <li>
     The G++ implementation of <a href="../projects/cxx1y.html">C++1y</a> return type deduction for normal
     functions has been updated to conform to
-    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3638.html">N3638</a>, 
+    <a href="https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3638.html">N3638</a>, 
     the proposal accepted into the working paper.  Most notably, it adds
     <code>decltype(auto)</code> for getting <code>decltype</code> semantics
     rather than the template argument deduction semantics of plain
@@ -312,7 +312,7 @@ auto add = [] wwwdocs: &lt;typename T&gt; (T a, T b) { return a + b; };
   <li>
     G++ supports unconstrained <em>generic functions</em> as specified
     by &sect;4.1.2 and &sect;5.1.1 of
-    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3889.pdf">
+    <a href="https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3889.pdf">
     N3889: Concepts Lite Specification</a>.  Briefly,
     <code>auto</code> may be used as a type-specifier in a parameter
     declaration of any function declarator in order to introduce an
-- 
2.39.0

                 reply	other threads:[~2023-01-19 14:48 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=20230119144841.1B7E233E8E@hamza.pair.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@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).