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. 1f9ebcc8f95b1e07b96b20eab377fb4cd418e936 Date: Mon, 20 Jul 2020 22:21:46 +0000 (GMT) [thread overview] Message-ID: <20200720222146.72FA73857C73@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 1f9ebcc8f95b1e07b96b20eab377fb4cd418e936 (commit) from d98ae5d85d52d99a797075a85a54c4603a564d25 (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 1f9ebcc8f95b1e07b96b20eab377fb4cd418e936 Author: Jason Merrill <jason@redhat.com> Date: Mon Jul 20 18:21:18 2020 -0400 cxx-status: C++20 pseudo-dtor EOL implemented. diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html index b56f1b46..c57e5573 100644 --- a/htdocs/projects/cxx-status.html +++ b/htdocs/projects/cxx-status.html @@ -566,7 +566,7 @@ <tr> <td>DR: Pseudo-destructors end object lifetimes</td> <td><a href="https://wg21.link/p0593r6">P0593R6</a></td> - <td class="unsupported">No</td> + <td class="supported center"><a href="../gcc-11/changes.html#cxx">11</a></td> <td></td> </tr> </table> ----------------------------------------------------------------------- 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-20 22:21 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=20200720222146.72FA73857C73@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: linkBe 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).