From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-block@nongnu.org, stefanha@redhat.com
Subject: Re: [PATCH v4 0/3] qcow2: Allow resize of images with internal snapshots
Date: Wed, 29 Apr 2020 10:55:34 +0200 [thread overview]
Message-ID: <308da480-e5ec-c9c0-9147-6bd6f761f2b2@redhat.com> (raw)
In-Reply-To: <20200428192648.749066-1-eblake@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 854 bytes --]
On 28.04.20 21:26, Eric Blake wrote:
> Re-posting this to make Max' life easier when rebasing on top of Kevin's work.
>
> Based-on: <20200424125448.63318-1-kwolf@redhat.com>
> [PATCH v7 00/10] block: Fix resize (extending) of short overlays
>
> In v4:
> - patch 1: fold in Max's touchups to my v3
> - patch 1: resolve merge conflict on top of Kevin's block-next branch (truncate signature change)
> - patch 2: resolve semantic conflict (truncate signature change)
>
> 001/3:[0004] [FC] 'block: Add blk_new_with_bs() helper'
> 002/3:[0002] [FC] 'qcow2: Allow resize of images with internal snapshots'
> 003/3:[----] [--] 'qcow2: Tweak comment about bitmaps vs. resize'
Thanks, I’ve updated my branch:
https://git.xanclic.moe/XanClic/qemu/commits/branch/block-next
(A commit with two Message-Id tags is interesting :))
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-04-29 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 19:26 [PATCH v4 0/3] qcow2: Allow resize of images with internal snapshots Eric Blake
2020-04-28 19:26 ` [PATCH v4 1/3] block: Add blk_new_with_bs() helper Eric Blake
2020-04-28 19:26 ` [PATCH v4 2/3] qcow2: Allow resize of images with internal snapshots Eric Blake
2020-04-28 19:26 ` [PATCH v4 3/3] qcow2: Tweak comment about bitmaps vs. resize Eric Blake
2020-04-29 8:55 ` Max Reitz [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=308da480-e5ec-c9c0-9147-6bd6f761f2b2@redhat.com \
--to=mreitz@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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 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).