From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com,
dplotnikov@virtuozzo.com, den@openvz.org
Subject: Re: [PATCH v11 0/2] docs: qcow2: introduce compression type feature
Date: Thu, 6 Feb 2020 17:30:19 +0300 [thread overview]
Message-ID: <e9ba9f1d-3f0c-b3e6-1ced-14c2dca94d67@virtuozzo.com> (raw)
In-Reply-To: <e84b1805-c0c0-eb74-8768-e4f6876117e0@redhat.com>
06.02.2020 16:51, Max Reitz wrote:
> On 31.01.20 15:22, Vladimir Sementsov-Ogievskiy wrote:
>> v11:
>> 01: grammar/wording [Eric]
>> add Eric's r-b
>> 02: empty lines between paragraphs [Eric]
>>
>> Vladimir Sementsov-Ogievskiy (2):
>> docs: improve qcow2 spec about extending image header
>> docs: qcow2: introduce compression type feature
>>
>> docs/interop/qcow2.txt | 62 ++++++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 59 insertions(+), 3 deletions(-)
>
> Thanks, I’ve fixed patch 1’s commit message and applied the series to my
> block branch:
>
> https://git.xanclic.moe/XanClic/qemu/commits/branch/block
>
Thanks!
--
Best regards,
Vladimir
prev parent reply other threads:[~2020-02-06 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 14:22 [PATCH v11 0/2] docs: qcow2: introduce compression type feature Vladimir Sementsov-Ogievskiy
2020-01-31 14:22 ` [PATCH v11 1/2] docs: improve qcow2 spec about extending image header Vladimir Sementsov-Ogievskiy
2020-01-31 14:46 ` Eric Blake
2020-01-31 17:13 ` Alberto Garcia
2020-01-31 14:22 ` [PATCH v11 2/2] docs: qcow2: introduce compression type feature Vladimir Sementsov-Ogievskiy
2020-01-31 14:46 ` Eric Blake
2020-01-31 17:34 ` Alberto Garcia
2020-01-31 17:49 ` Eric Blake
2020-01-31 18:15 ` Vladimir Sementsov-Ogievskiy
2020-01-31 22:14 ` Alberto Garcia
2020-02-06 12:38 ` Max Reitz
2020-02-06 14:08 ` Eric Blake
2020-02-06 13:51 ` [PATCH v11 0/2] " Max Reitz
2020-02-06 14:30 ` Vladimir Sementsov-Ogievskiy [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=e9ba9f1d-3f0c-b3e6-1ced-14c2dca94d67@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=dplotnikov@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).