From: Eric Blake <eblake@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [qemu-kvm PATCH] block: vhdx - improve error message, and .bdrv_check implementation
Date: Tue, 17 Dec 2013 08:44:54 -0700 [thread overview]
Message-ID: <52B07176.6040107@redhat.com> (raw)
In-Reply-To: <20131217153830.GC4333@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
On 12/17/2013 08:38 AM, Jeff Cody wrote:
>>
>>> + error_setg_errno(errp, EPERM,
>>> + "VHDX image file '%s' opened read-only, but "
>>> + "contains a log that needs replayed. To replay "
>>
>> s/replayed/replaying/
>>
>
> How about "to be replayed" instead? "Replaying", while correct, just
> sounds a bit off to me.
Yes, that works as well.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-12-17 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 10:33 [Qemu-devel] [qemu-kvm PATCH] block: vhdx - improve error message, and .bdrv_check implementation Jeff Cody
2013-12-17 13:56 ` Eric Blake
2013-12-17 15:38 ` Jeff Cody
2013-12-17 15:44 ` Eric Blake [this message]
2013-12-18 13:52 ` Stefan Hajnoczi
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=52B07176.6040107@redhat.com \
--to=eblake@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.