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. f1f7f774224a1580c9aad4b0f496626afc531adc Date: Thu, 7 Apr 2022 15:05:28 +0000 (GMT) [thread overview] Message-ID: <20220407150528.C342538515F3@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 f1f7f774224a1580c9aad4b0f496626afc531adc (commit) from 7e3ef4042601fb155f4331804f35849d7f20e8c2 (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 f1f7f774224a1580c9aad4b0f496626afc531adc Author: Marek Polacek <polacek@redhat.com> Date: Thu Apr 7 11:05:16 2022 -0400 gcc-12: Fix typo diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index 4f2ee77f..4cfe2bf5 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -308,7 +308,7 @@ a work-in-progress.</p> <code>-Wc++11-extensions</code>, <code>-Wc++14-extensions</code>, <code>-Wc++17-extensions</code>, <code>-Wc++20-extensions</code>, and <code>-Wc++23-extensions</code>. They are enabled by default - and can be used to control existing pedwarns about occurences of + and can be used to control existing pedwarns about occurrences of new C++ constructs in code using an old C++ standard dialect.</li> <li>New warning <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wmissing-requires"><code>-Wmissing-requires</code></a> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-04-07 15:05 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=20220407150528.C342538515F3@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).