public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jason Merrill <jason@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 99cd379b52ace0da0f27cfed5b87f0b614771952
Date: Wed, 29 Jul 2020 18:26:57 +0000 (GMT) [thread overview]
Message-ID: <20200729182657.970993857C71@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 99cd379b52ace0da0f27cfed5b87f0b614771952 (commit)
from dc78a1aaaeab65cb59d078b565b470c8dcc515d0 (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 99cd379b52ace0da0f27cfed5b87f0b614771952
Author: Jason Merrill <jason@redhat.com>
Date: Wed Jul 29 14:26:42 2020 -0400
cxx-status: C++20 implicit moves.
diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index c57e5573..c1722384 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/cxx-status.html
@@ -559,7 +559,7 @@
<tr>
<td>DR: More implicit moves (merge P0527R1 and P1155R3)</td>
<td><a href="https://wg21.link/p1825r0">P1825R0</a></td>
- <td class="unsupported">No (<a href="https://gcc.gnu.org/PR91427">PR91427</a>)</td>
+ <td class="supported center"><a href="../gcc-11/changes.html#cxx">11</a> (C++20 mode)</td>
<td></td>
</tr>
<!-- Prague 2019 papers -->
-----------------------------------------------------------------------
Summary of changes:
htdocs/projects/cxx-status.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
gcc-wwwdocs
reply other threads:[~2020-07-29 18:26 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=20200729182657.970993857C71@sourceware.org \
--to=jason@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).