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. ba66d93e131a74ccc0fa4551b9a288ec38556ddc Date: Thu, 18 Nov 2021 23:16:33 +0000 (GMT) [thread overview] Message-ID: <20211118231633.9F7F63858014@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 ba66d93e131a74ccc0fa4551b9a288ec38556ddc (commit) from 97c063b9e45250da2ca9b9d527000f437d92e093 (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 ba66d93e131a74ccc0fa4551b9a288ec38556ddc Author: Marek Polacek <polacek@redhat.com> Date: Thu Nov 18 18:16:18 2021 -0500 cxx-status: C++23 auto(x) supported diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html index d2d6eab4..1a4f9d86 100644 --- a/htdocs/projects/cxx-status.html +++ b/htdocs/projects/cxx-status.html @@ -197,8 +197,8 @@ <!-- https://github.com/cplusplus/papers/issues/293 --> <tr> <td> auto(x): decay-copy in the language </td> - <td> <a href="https://wg21.link/p849r8">P849R8</a></td> - <td class="unsupported"> <a href="https://gcc.gnu.org/PR103049">No</a></td> + <td> <a href="https://wg21.link/p0849r8">P0849R8</a></td> + <td class="supported"> <a href="../gcc-12/changes.html#cxx">12</a></td> <td> </td> </tr> <tr> ----------------------------------------------------------------------- Summary of changes: htdocs/projects/cxx-status.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-11-18 23:16 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=20211118231633.9F7F63858014@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: 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).