public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. e76e98a2a9d833bc22c3bf25950298b3a8905391
Date: Sat,  5 Nov 2022 22:58:54 +0000 (GMT)	[thread overview]
Message-ID: <20221105225854.052643858C56@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  e76e98a2a9d833bc22c3bf25950298b3a8905391 (commit)
      from  8ee48d6db8b318d4f332cb993c52667bfe0e8dfd (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit e76e98a2a9d833bc22c3bf25950298b3a8905391
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sat Nov 5 23:58:22 2022 +0100

    gcc-4.8: Move three links from http to https

diff --git a/htdocs/gcc-4.8/changes.html b/htdocs/gcc-4.8/changes.html
index 39557435..cb30a5e9 100644
--- a/htdocs/gcc-4.8/changes.html
+++ b/htdocs/gcc-4.8/changes.html
@@ -258,7 +258,7 @@ B b(42); // OK
 </pre></blockquote>
   </li>
 
-  <li>As of GCC 4.8.1, G++ implements the change to <code>decltype</code> semantics from <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3276.pdf">N3276</a>.
+  <li>As of GCC 4.8.1, G++ implements the change to <code>decltype</code> semantics from <a href="https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3276.pdf">N3276</a>.
 <blockquote><pre>
 struct A f();
 decltype(f()) g();    // OK, return type of f() is not required to be complete.
@@ -276,7 +276,7 @@ int i = A().f();  // error, f() requires an lvalue object
     with features proposed for the next revision of the standard, expected
     around 2014.  Currently the only difference from <code>-std=c++11</code>
     is support for return type deduction in normal functions, as proposed in 
-    <a href="http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2012/n3386.html">N3386</a>.
+    <a href="https://www.open-std.org/JTC1/SC22/WG21/docs/papers/2012/n3386.html">N3386</a>.
     Status of C++1y features in GCC 4.8 can be found <a href="../projects/cxx1y.html">here</a>.
   </li>
 
@@ -436,7 +436,7 @@ int i = A().f();  // error, f() requires an lvalue object
       gfortran's own array descriptor is used, which is different from the
       one defined in TS29113, see <a
       href="https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=libgfortran/libgfortran.h">gfortran's header file</a> or use the <a
-      href="http://chasm-interop.sourceforge.net/">Chasm Language
+      href="https://chasm-interop.sourceforge.net/">Chasm Language
       Interoperability Tools</a>.</li>
     </ul></li>
   </ul>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-4.8/changes.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2022-11-05 22:58 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=20221105225854.052643858C56@sourceware.org \
    --to=gerald@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).