From: Thomas Huth <thuth@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, Eric Blake <eblake@redhat.com>
Cc: qemu-trivial@nongnu.org
Subject: [PATCH] qapi/pragma.json: Improve the comment about the lists of QAPI rule exceptions
Date: Mon, 13 Nov 2023 17:29:28 +0100 [thread overview]
Message-ID: <20231113162928.54551-1-thuth@redhat.com> (raw)
Let's use more inclusive language here.
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
qapi/pragma.json | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/qapi/pragma.json b/qapi/pragma.json
index 7f810b0e97..0aa4eeddd3 100644
--- a/qapi/pragma.json
+++ b/qapi/pragma.json
@@ -3,8 +3,8 @@
{ 'pragma': { 'doc-required': true } }
-# Whitelists to permit QAPI rule violations; think twice before you
-# add to them!
+# Entries in these lists are allowed to violate the QAPI rules (for
+# historical reasons); think twice before you add to them!
{ 'pragma': {
# Command names containing '_'
'command-name-exceptions': [
--
2.41.0
next reply other threads:[~2023-11-13 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 16:29 Thomas Huth [this message]
2023-11-14 16:39 ` [PATCH] qapi/pragma.json: Improve the comment about the lists of QAPI rule exceptions Eric Blake
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=20231113162928.54551-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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: 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 NNTP newsgroup(s).