public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Marek Polacek <mpolacek@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. ff469cb03433b10c7b4332b7f91951078111d9ae
Date: Mon, 10 Aug 2020 17:58:37 +0000 (GMT)	[thread overview]
Message-ID: <20200810175837.14389385702F@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  ff469cb03433b10c7b4332b7f91951078111d9ae (commit)
      from  bcb7bb80fa2eeba28eb09845b0586950733d2fbb (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 ff469cb03433b10c7b4332b7f91951078111d9ae
Author: Marek Polacek <polacek@redhat.com>
Date:   Mon Aug 10 13:58:22 2020 -0400

    Fix the typo harder.

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index eb6687fa..54c638dd 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -112,7 +112,7 @@ a work-in-progress.</p>
   </li>
   <li>G++ now performs better access checking in templates
       (<a href="https://gcc.gnu.org/PR41437">PR41437</a>).</li>
-  <li><code>reinterpret_casts</code>s in constexpr evaluation are now checked
+  <li><code>reinterpret_cast</code>s in constexpr evaluation are now checked
       more completely (<a href="https://gcc.gnu.org/PR95307">PR95307</a>).</li>
 </ul>
 

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-08-10 17: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=20200810175837.14389385702F@sourceware.org \
    --to=mpolacek@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).