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. f710d6259eb22d0325b9481a00898b3fc318874e Date: Fri, 18 Nov 2022 18:09:37 +0000 (GMT) [thread overview] Message-ID: <20221118180937.3CA9D385841C@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 f710d6259eb22d0325b9481a00898b3fc318874e (commit) from 290f0026fcde3b18b60eb363dffe7db14ff1bc2d (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 f710d6259eb22d0325b9481a00898b3fc318874e Author: Marek Polacek <polacek@redhat.com> Date: Fri Nov 18 13:09:13 2022 -0500 cxx-status: P2647R1 no longer DR diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html index 9adf46f0..e2625003 100644 --- a/htdocs/projects/cxx-status.html +++ b/htdocs/projects/cxx-status.html @@ -365,7 +365,7 @@ </tr> <!-- Kona 2022, https://github.com/cplusplus/papers/issues/1318 --> <tr> - <td> DR: Permitting <code>static constexpr</code> variables in + <td> Permitting <code>static constexpr</code> variables in <code>constexpr</code> functions </td> <td> <a href="https://wg21.link/p2647">P2647R1</a></td> <td class="unsupported"> <a href="https://gcc.gnu.org/PR107685">No</a></td> ----------------------------------------------------------------------- Summary of changes: htdocs/projects/cxx-status.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-11-18 18:09 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=20221118180937.3CA9D385841C@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).