From: John Snow <jsnow@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] spec/parallels: fix a mistake
Date: Thu, 30 Jun 2016 13:16:57 -0400 [thread overview]
Message-ID: <ff5f201f-5ab7-354f-bc1b-683a8d22b559@redhat.com> (raw)
In-Reply-To: <57755302.7060908@openvz.org>
On 06/30/2016 01:12 PM, Denis V. Lunev wrote:
> On 06/30/2016 07:43 PM, John Snow wrote:
>>
>> On 06/30/2016 04:15 AM, Vladimir Sementsov-Ogievskiy wrote:
>>> We have only one flag for now - Empty Image flag.
>>>
>>> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>>> ---
>>> docs/specs/parallels.txt | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/docs/specs/parallels.txt b/docs/specs/parallels.txt
>>> index b4fe229..e9271eb 100644
>>> --- a/docs/specs/parallels.txt
>>> +++ b/docs/specs/parallels.txt
>>> @@ -94,7 +94,7 @@ Bytes:
>>> Bit 0: Empty Image bit. If set, the image should be
>>> considered clear.
>>> - Bits 2-31: Unused.
>>> + Bits 1-31: Unused.
>>> 56 - 63: ext_off
>>> Format Extension offset, an offset, in sectors, from
>>> the start of
>>>
>> Looks correct to me, but Denis should confirm.
>>
>> --js
> Funny ;)
>
> I have already resent the version with a bit improved
> description, which was takes by Stefan.
>
> Thank you for paying attention.
>
> Den
I wouldn't normally pay attention to parallels spec changes, but this
one made it to my inbox. :)
prev parent reply other threads:[~2016-06-30 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 8:15 [Qemu-devel] [PATCH] spec/parallels: fix a mistake Vladimir Sementsov-Ogievskiy
2016-06-30 16:43 ` John Snow
2016-06-30 17:12 ` Denis V. Lunev
2016-06-30 17:16 ` John Snow [this message]
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=ff5f201f-5ab7-354f-bc1b-683a8d22b559@redhat.com \
--to=jsnow@redhat.com \
--cc=den@openvz.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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 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).