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. f834612fa014a65bd0a0380d2167d9ee05626a64 Date: Fri, 12 Jan 2024 05:55:07 +0000 (GMT) [thread overview] Message-ID: <20240112055507.1DBC43858D1E@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 f834612fa014a65bd0a0380d2167d9ee05626a64 (commit) from f2dcdb8c1d4c3075fdbf00adc6d38347b83e73de (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 f834612fa014a65bd0a0380d2167d9ee05626a64 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Fri Jan 12 13:54:52 2024 +0800 gcc-14: Fix markup around -fcf-protection diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index ba57abe8..9c9dfa44 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -41,9 +41,9 @@ a work-in-progress.</p> identify all such cases in the source code and modify them. </li> <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html"><code>-fcf-protection=[full|branch|return|none|check]</code></a> - is refactored, to override <code>-fcf-protection<code>, - <code>-fcf-protection=none<code> needs to be added and then - with <code>-fcf-protection=xxx<code>. + is refactored, to override <code>-fcf-protection</code>, + <code>-fcf-protection=none</code> needs to be added and then + with <code>-fcf-protection=xxx</code>. </li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-14/changes.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-01-12 5:55 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=20240112055507.1DBC43858D1E@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).