From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org, Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: [PATCH 06/24] docs: spelling fixes
Date: Wed, 23 Aug 2023 09:30:26 +0100 [thread overview]
Message-ID: <87r0nugewa.fsf@linaro.org> (raw)
In-Reply-To: <20230823065335.1919380-5-mjt@tls.msk.ru>
Michael Tokarev <mjt@tls.msk.ru> writes:
> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
> ---
> docs/devel/qapi-code-gen.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/docs/devel/qapi-code-gen.rst b/docs/devel/qapi-code-gen.rst
> index 7f78183cd4..b0852da97b 100644
> --- a/docs/devel/qapi-code-gen.rst
> +++ b/docs/devel/qapi-code-gen.rst
> @@ -1368,5 +1368,5 @@ anymore, optional return or event data members that can't be sent
> anymore, and return or event data member (enumeration) values that
> can't be sent anymore makes no difference to clients, except for
> -introspection. The latter can conceivably confuse clients, so tread
> +introspection. The latter can conceivably confuse clients, so treat
> carefully.
I guess this is a cultural idiom because "tread carefully" is a common
phrase in British English at least. For example:
Investors need to tread carefully, as irrational exuberance has a
habit of eclipsing common sense in the world of tech.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-08-23 11:52 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 5:51 [PATCH v2 00/24] tree-wide spelling fixes Michael Tokarev
2023-08-23 5:51 ` [PATCH 01/24] block: " Michael Tokarev
2023-08-23 18:16 ` Eric Blake
2023-08-23 6:26 ` [PATCH v2 00/24] tree-wide " Michael Tokarev
2023-08-23 6:53 ` [PATCH 02/24] bsd-user: " Michael Tokarev
2023-08-23 6:53 ` [PATCH 03/24] ui: " Michael Tokarev
2023-08-23 6:53 ` [PATCH 04/24] util: " Michael Tokarev
2023-08-24 10:10 ` Philippe Mathieu-Daudé
2023-08-23 6:53 ` [PATCH 05/24] tcg: " Michael Tokarev
2023-08-23 8:30 ` Alex Bennée
2023-08-23 20:05 ` Richard Henderson
2023-08-23 6:53 ` [PATCH 06/24] docs: " Michael Tokarev
2023-08-23 8:30 ` Alex Bennée [this message]
2023-08-23 12:06 ` Michael Tokarev
2023-08-23 6:53 ` [PATCH 07/24] i386: " Michael Tokarev
2023-08-23 6:53 ` [PATCH 08/24] mips: " Michael Tokarev
2023-08-24 10:11 ` Philippe Mathieu-Daudé
2023-08-23 6:53 ` [PATCH 09/24] ppc: " Michael Tokarev
2023-08-23 6:53 ` [PATCH 10/24] riscv: " Michael Tokarev
2023-08-23 6:53 ` [PATCH 11/24] hexagon: " Michael Tokarev
2023-08-23 15:36 ` Brian Cain
2023-08-23 6:53 ` [PATCH 12/24] hw/net: " Michael Tokarev
2023-08-23 6:53 ` [PATCH 13/24] hw/pci: " Michael Tokarev
2023-08-23 6:53 ` [PATCH 14/24] hw/tpm: " Michael Tokarev
2023-08-23 6:53 ` [PATCH 15/24] hw/usb hw/ide hw/i2c: " Michael Tokarev
2023-08-23 6:53 ` [PATCH 16/24] hw/display: " Michael Tokarev
2023-08-24 10:12 ` Philippe Mathieu-Daudé
2023-08-24 11:46 ` Michael Tokarev
2023-08-24 12:26 ` Peter Maydell
2023-08-23 6:53 ` [PATCH 17/24] xen: " Michael Tokarev
2023-08-23 18:38 ` David Woodhouse
2023-08-23 19:00 ` Michael Tokarev
2023-08-25 8:52 ` David Woodhouse
2023-08-23 6:53 ` [PATCH 18/24] audio: " Michael Tokarev
2023-08-24 10:13 ` Philippe Mathieu-Daudé
2023-08-23 6:53 ` [PATCH 19/24] hw/other: " Michael Tokarev
2023-08-23 6:53 ` [PATCH 20/24] include/: " Michael Tokarev
2023-08-23 14:09 ` Alex Bennée
2023-08-23 6:53 ` [PATCH 21/24] scripts/: " Michael Tokarev
2023-08-23 14:13 ` Alex Bennée
2023-08-23 19:12 ` Michael Tokarev
2023-08-23 19:26 ` Michael Tokarev
2023-08-23 6:53 ` [PATCH 22/24] tests/: " Michael Tokarev
2023-08-23 6:53 ` [PATCH 23/24] qga/: " Michael Tokarev
2023-08-23 6:53 ` [PATCH 24/24] misc/other: " Michael Tokarev
2023-08-23 18:23 ` Eric Blake
2023-08-23 19:11 ` Michael Tokarev
-- strict thread matches above, loose matches on Subject: below --
2023-08-07 10:56 [PATCH trivial for-8.1 0/3] trivial-patches for 2023-08-07 Michael Tokarev
2023-08-23 5:51 ` [PATCH 06/24] docs: spelling fixes Michael Tokarev
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=87r0nugewa.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@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).