public inbox for
help / color / mirror / Atom feed
From: Gerald Pfeifer <>
Subject: gcc-wwwdocs branch master updated. c1c81722793cc028d4c3025d3c350876025b5a84
Date: Fri, 27 Jan 2023 00:23:25 +0000 (GMT)	[thread overview]
Message-ID: <> (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  c1c81722793cc028d4c3025d3c350876025b5a84 (commit)
      from  cf6ceb538ac57dc95e6aac741c9c7ada5f4cfee4 (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 c1c81722793cc028d4c3025d3c350876025b5a84
Author: Gerald Pfeifer <>
Date:   Fri Jan 27 01:23:04 2023 +0100

    gcc-3.4: Update a link to use https

diff --git a/htdocs/gcc-3.4/changes.html b/htdocs/gcc-3.4/changes.html
index d9985673..76b4ce87 100644
--- a/htdocs/gcc-3.4/changes.html
+++ b/htdocs/gcc-3.4/changes.html
@@ -521,7 +521,7 @@ and not your code, that is broken.</em></p>
         Previous versions of G++ used to be less strict about this and
         allowed friend declarations for <code>private</code> class members,
         for example.  See the ISO C++ Standard Committee's <a
-        href="">defect
+        href="">defect
         report #209</a> for details.</li>
     <li>Declaration of member functions of class templates as friends are


Summary of changes:
 htdocs/gcc-3.4/changes.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


                 reply	other threads:[~2023-01-27  0:23 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).