All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhao Liu <zhao1.liu@intel.com>
To: Samuel Tardieu <sam@rfc1149.net>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, Hanna Reitz <hreitz@redhat.com>,
	qemu-trivial@nongnu.org
Subject: Re: [PATCH] docs: fix typo
Date: Fri, 15 Dec 2023 10:59:00 +0800	[thread overview]
Message-ID: <ZXvA9IlOEZfVNzuO@intel.com> (raw)
In-Reply-To: <20231214225318.2391800-1-sam@rfc1149.net>

On Thu, Dec 14, 2023 at 11:53:18PM +0100, Samuel Tardieu wrote:
> Date: Thu, 14 Dec 2023 23:53:18 +0100
> From: Samuel Tardieu <sam@rfc1149.net>
> Subject: [PATCH] docs: fix typo
> X-Mailer: git-send-email 2.42.0
> 
> Signed-off-by: Samuel Tardieu <sam@rfc1149.net>
> ---

Reviewed-by: Zhao Liu <zhao1.liu@intel.com>

>  docs/tools/qemu-img.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/docs/tools/qemu-img.rst b/docs/tools/qemu-img.rst
> index 4459c065f1..3653adb963 100644
> --- a/docs/tools/qemu-img.rst
> +++ b/docs/tools/qemu-img.rst
> @@ -406,7 +406,7 @@ Command description:
>    Compare exits with ``0`` in case the images are equal and with ``1``
>    in case the images differ. Other exit codes mean an error occurred during
>    execution and standard error output should contain an error message.
> -  The following table sumarizes all exit codes of the compare subcommand:
> +  The following table summarizes all exit codes of the compare subcommand:
>  
>    0
>      Images are identical (or requested help was printed)
> -- 
> 2.42.0
> 
> 


  reply	other threads:[~2023-12-15  5:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 22:53 [PATCH] docs: fix typo Samuel Tardieu
2023-12-15  2:59 ` Zhao Liu [this message]
2023-12-23 16:36 ` Michael Tokarev
  -- strict thread matches above, loose matches on Subject: below --
2024-10-02 10:58 [PATCH] docs: Fix typo KK Surendran
2024-10-02 13:40 ` Guenter Roeck
2024-10-02 10:13 KK Surendran
2022-08-01 18:10 [PATCH] docs: Fix Typo Max Dunbar
2022-08-08 15:59 ` Guenter Roeck

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=ZXvA9IlOEZfVNzuO@intel.com \
    --to=zhao1.liu@intel.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=sam@rfc1149.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.