public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Qing Zhao <qinzhao@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. fc681f5412c421ff9609aea448310106d2570fd5 Date: Tue, 17 Jan 2023 15:53:00 +0000 (GMT) [thread overview] Message-ID: <20230117155300.708913858D28@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 fc681f5412c421ff9609aea448310106d2570fd5 (commit) from dcb59089cf4bd7f09f273d7b3f35c568b1d407fb (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 fc681f5412c421ff9609aea448310106d2570fd5 Author: Qing Zhao <qing.zhao@oracle.com> Date: Tue Jan 17 15:52:15 2023 +0000 gcc13/changes: update id 'flexible array' to 'flexible-arrays' since ids must not contain white space diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 08e36fb3..ca9cd2da 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -438,7 +438,7 @@ a work-in-progress.</p> <h2>Other significant improvements</h2> <!-- <h3 id="uninitialized">Eliminating uninitialized variables</h3> --> -<h3 id="flexible array">Treating trailing arrays as flexible array members</h3> +<h3 id="flexible-arrays">Treating trailing arrays as flexible array members</h3> <ul> <li>GCC can now control when to treat the trailing array of a structure as a ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-01-17 15:53 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=20230117155300.708913858D28@sourceware.org \ --to=qinzhao@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).