public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 864728361f39f6251fe1774a6ae66ac40657737b
Date: Tue, 14 Feb 2023 10:34:25 +0000 (GMT) [thread overview]
Message-ID: <20230214103425.3C8B53858D1E@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 864728361f39f6251fe1774a6ae66ac40657737b (commit)
from 961f145700ceeed13627bc8e20e23afd26322f9d (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 864728361f39f6251fe1774a6ae66ac40657737b
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Feb 14 11:34:09 2023 +0100
Add feature test macro for P2718R0.
diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index cc8fe615..b5362bba 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/cxx-status.html
@@ -390,7 +390,7 @@
<td> Wording for P2644R1 Fix for Range-based for Loop </td>
<td> <a href="https://wg21.link/p2718">P2718R0</a></td>
<td class="unsupported"> <a href="https://gcc.gnu.org/PR107637">No</a></td>
- <td> </td>
+ <td> __cpp_range_based_for >= 202211L </td>
</tr>
<!--
<tr>
-----------------------------------------------------------------------
Summary of changes:
htdocs/projects/cxx-status.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
gcc-wwwdocs
reply other threads:[~2023-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=20230214103425.3C8B53858D1E@sourceware.org \
--to=jakub@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).