From: Joseph Myers <joseph@codesourcery.com>
To: Qing Zhao <qing.zhao@oracle.com>
Cc: <richard.guenther@gmail.com>, <jakub@redhat.com>,
<gcc-patches@gcc.gnu.org>, <keescook@chromium.org>,
<siddhesh@gotplt.org>, <uecker@tugraz.at>
Subject: Re: [V8][PATCH 2/2] Update documentation to clarify a GCC extension [PR77650]
Date: Thu, 25 May 2023 20:51:08 +0000 [thread overview]
Message-ID: <e16e525a-cb1-5e15-59f0-74bdd4f3d7ae@codesourcery.com> (raw)
In-Reply-To: <20230525152821.2989599-3-qing.zhao@oracle.com>
The documentation in this case is OK, though claims about how a future
version will behave have a poor track record (we tend to end up with such
claims persisting in the documentation even though the change in question
didn't get made and might sometimes no longer be considered desirable).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-05-25 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 15:28 [V8][PATCH 0/2]Accept and Handle the case when a structure including a FAM nested in another structure Qing Zhao
2023-05-25 15:28 ` [V8][PATCH 1/2] Handle component_ref to a structre/union field including flexible array member [PR101832] Qing Zhao
2023-05-25 15:28 ` [V8][PATCH 2/2] Update documentation to clarify a GCC extension [PR77650] Qing Zhao
2023-05-25 20:51 ` Joseph Myers [this message]
2023-05-25 23:59 ` Qing Zhao
2023-05-26 17:59 ` Joseph Myers
2023-05-26 19:07 ` Qing Zhao
2023-05-26 20:12 ` Joseph Myers
2023-05-30 15:29 ` Qing Zhao
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=e16e525a-cb1-5e15-59f0-74bdd4f3d7ae@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=keescook@chromium.org \
--cc=qing.zhao@oracle.com \
--cc=richard.guenther@gmail.com \
--cc=siddhesh@gotplt.org \
--cc=uecker@tugraz.at \
/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: link
Be 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).