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. d364554e59c6d5d8b8a8c438921b3cfd061e43a1 Date: Thu, 1 Sep 2022 09:26:21 +0000 (GMT) [thread overview] Message-ID: <20220901092621.6EB4438582A6@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 d364554e59c6d5d8b8a8c438921b3cfd061e43a1 (commit) from 5fb39f38b5589d94d859f1e5d32f98db84f7036f (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 d364554e59c6d5d8b8a8c438921b3cfd061e43a1 Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Sep 1 11:25:07 2022 +0200 Mention implementation of P2295R6 - strict UTF-8 source is only when -finput-charset=UTF-8 is used. diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html index fec65c24..af3cb824 100644 --- a/htdocs/projects/cxx-status.html +++ b/htdocs/projects/cxx-status.html @@ -323,7 +323,7 @@ <tr> <td> Support for UTF-8 as a portable source file encoding </td> <td> <a href="https://wg21.link/p2295r6">P2295R6</a></td> - <td class="unsupported"> <a href="https://gcc.gnu.org/PR106655">No</a></td> + <td class="supported"> <a href="../gcc-13/changes.html#cxx">13</a></td> <td> </td> </tr> <!-- https://github.com/cplusplus/papers/issues/1171 --> ----------------------------------------------------------------------- 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-09-01 9:26 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=20220901092621.6EB4438582A6@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: 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).