public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 805fec94cc717ef843722320265612989b585bb0 Date: Sat, 30 Jul 2022 21:33:20 +0000 (GMT) [thread overview] Message-ID: <20220730213320.D5BFA3858413@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 805fec94cc717ef843722320265612989b585bb0 (commit) from 9b3dbc6dd9e278edde818fe123ae13ffe2d639f9 (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 805fec94cc717ef843722320265612989b585bb0 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Sat Jul 30 23:32:41 2022 +0200 cxx-status: Fix erroneous entry from previous commit diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html index ae0321c0..2d45e82e 100644 --- a/htdocs/projects/cxx-status.html +++ b/htdocs/projects/cxx-status.html @@ -1336,7 +1336,7 @@ </tr> <tr> <td>Non-static data member initializers</td> - <td><a href="https://www.open-std.org/JTC1/SC22/WG21/docs/papers/2008/n2756.htm"</a></td> + <td><a href="https://www.open-std.org/JTC1/SC22/WG21/docs/papers/2008/n2756.htm">N2756</a></td> <td><a href="../gcc-4.7/changes.html">GCC 4.7</a></td> <td>__cpp_nsdmi >= 200809</td> </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:[~2022-07-30 21:33 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=20220730213320.D5BFA3858413@sourceware.org \ --to=gerald@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).