public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: jakub@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 3b68ceb3fd62e93f44a4a6f57d1f0e13c1145a87 Date: Fri, 14 Feb 2020 10:34:00 -0000 [thread overview] Message-ID: <20200214103452.76775.qmail@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 3b68ceb3fd62e93f44a4a6f57d1f0e13c1145a87 (commit) from e37f2d6af29c52a51cb36058e3a7a2b79469f045 (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 3b68ceb3fd62e93f44a4a6f57d1f0e13c1145a87 Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Feb 14 11:34:23 2020 +0100 wwwdocs: Clarify C++20 P1042R1 is only partially supported and only since GCC10 diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html index f698393d..3f69d443 100644 --- a/htdocs/projects/cxx-status.html +++ b/htdocs/projects/cxx-status.html @@ -86,7 +86,9 @@ <td><a href="http://wg21.link/p0306r4">P0306R4</a><br/> <a href="http://wg21.link/p1042r1">P1042R1</a></td> <td class="partial"> <a href="../gcc-8/changes.html#cxx">8</a> - (partial, no <code>#__VA_OPT__</code> support) </td> + (partial, no <code>#__VA_OPT__</code> support) <br/> + <a href="../gcc-10/changes.html#cxx">10</a> + (partial, no placemarker token handling changes)</td> <td> </td> </tr> <tr> ----------------------------------------------------------------------- Summary of changes: htdocs/projects/cxx-status.html | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-02-14 10:34 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=20200214103452.76775.qmail@sourceware.org \ --to=jakub@gcc.gnu.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).