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. fb070b2eea6f8f0812360ea20f323e867690bdd4
Date: Fri, 26 Aug 2022 14:14:56 +0000 (GMT)	[thread overview]
Message-ID: <20220826141456.4BE2D3858427@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  fb070b2eea6f8f0812360ea20f323e867690bdd4 (commit)
      from  481413e0fa0cda049e42a343ae8f63ca3627eff1 (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 fb070b2eea6f8f0812360ea20f323e867690bdd4
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Aug 26 16:14:35 2022 +0200

    Say that P2460R2 is implemented forever.

diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index 5e99d11b..fec65c24 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/cxx-status.html
@@ -337,7 +337,7 @@
     <tr>
       <td> Relax requirements on <code>wchar_t</code> to match existing practices </td>
       <td> <a href="https://wg21.link/p2460r2">P2460R2</a></td>
-      <td class="unsupported"> <a href="https://gcc.gnu.org/PR106657">No</a></td>
+      <td class="supported">Yes</td>
       <td> </td>
     </tr>
     <!-- https://github.com/cplusplus/papers/issues/1248 -->

-----------------------------------------------------------------------

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-08-26 14:14 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=20220826141456.4BE2D3858427@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).