From: Max Reitz <mreitz@redhat.com>
To: Shravan Rajinikanth <shravan2x@utexas.edu>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] qemu-img: Fixed grammatical error in dump_human_image_check
Date: Fri, 2 Feb 2018 14:37:29 +0100 [thread overview]
Message-ID: <be898714-bffb-7fdf-0b91-e3c276559fc7@redhat.com> (raw)
In-Reply-To: <1512254273-7567-1-git-send-email-shravan2x@utexas.edu>
[-- Attachment #1.1: Type: text/plain, Size: 934 bytes --]
On 2017-12-02 23:37, Shravan Rajinikanth wrote:
> Signed-off-by: Shravan Rajinikanth <shravan2x@utexas.edu>
> ---
> qemu-img.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/qemu-img.c b/qemu-img.c
> index 68b375f..bea9268 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -580,7 +580,7 @@ static void dump_human_image_check(ImageCheck *check, bool quiet)
> if (check->leaks) {
> qprintf(quiet,
> "\n%" PRId64 " leaked clusters were found on the image.\n"
> - "This means waste of disk space, but no harm to data.\n",
> + "This means disk space is wasted, but data is safe.\n",
> check->leaks);
> }
Sorry, somehow I never applied this. (Maybe I thought it would go
through trivial...)
Applied to my block tree:
https://github.com/XanClic/qemu/commits/block
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2018-02-02 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 22:37 [Qemu-trivial] [PATCH] qemu-img: Fixed grammatical error in dump_human_image_check Shravan Rajinikanth
2017-12-04 15:44 ` [Qemu-trivial] [Qemu-devel] " Fam Zheng
2017-12-04 15:51 ` Max Reitz
2017-12-04 15:57 ` Peter Maydell
2017-12-04 20:44 ` Shravan Rajinikanth
2018-02-02 13:37 ` Max Reitz [this message]
2018-02-02 15:36 ` Max Reitz
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=be898714-bffb-7fdf-0b91-e3c276559fc7@redhat.com \
--to=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=shravan2x@utexas.edu \
/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).