From: Eric Blake <eblake@redhat.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-img rebase: allow backing file to be specified as '-'
Date: Mon, 15 Oct 2012 13:28:11 -0600 [thread overview]
Message-ID: <507C63CB.7090006@redhat.com> (raw)
In-Reply-To: <7C9D50488E80F46BDF7A16DA@Ximines.local>
[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]
On 10/15/2012 12:42 PM, Alex Bligh wrote:
> Eric,
>
> --On 15 October 2012 12:11:02 -0600 Eric Blake <eblake@redhat.com> wrote:
>
>> On the other hand, if you don't use -u, then qemu-img complains:
>>
>> $ qemu-img rebase -b '' bar
>> qemu-img: Could not open new backing file ''
>>
>> So I think a better patch would be to allow rebase-by-pull to work the
>> same as unsafe rebase, by honoring the empty string as a request to pull
>> the entire chain into the destination and leave no backing file.
>
> Yes, that's exactly the case we're missing. How about the attached (as
> a single patch)
>
> Also available at:
> https://github.com/abligh/qemu
> as commits
> https://github.com/abligh/qemu/commit/4cce9c961fa52a71bd6520a9c499f4dc4b174b97
>
> and
> https://github.com/abligh/qemu/commit/4d5b3b431d8dd276f4c564d8a82c6d25cb111381
>
>
> --
> Alex Bligh
Missing a Signed-off-by; as such, it cannot be taken as is. Please
repost, and provide an updated subject line and a dedicated commit
message (information such as where to download the commit for testing
belongs after the --- line). I'm not maintainer for this portion of
code, so I can only review it.
> @@ -1580,7 +1581,7 @@ static int img_rebase(int argc, char **argv)
> if (!unsafe) {
> uint64_t num_sectors;
> uint64_t old_backing_num_sectors;
> - uint64_t new_backing_num_sectors;
> + uint64_t new_backing_num_sectors=0;
As long as you are touching this line, fix the indentation to be
consistent (or is this unusual spacing an artifact of how you pasted
your commit after your '-- ' signature rather than submitting it via
'git send-email' as a proper patch?). Also, most of qemu uses spaces on
both sides of '='.
But the overall idea looks nice.
--
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: 617 bytes --]
next prev parent reply other threads:[~2012-10-15 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 17:29 [Qemu-devel] [PATCH] qemu-img rebase: allow backing file to be specified as '-' Alex Bligh
2012-10-15 18:07 ` Eric Blake
2012-10-15 18:11 ` Eric Blake
2012-10-15 18:42 ` Alex Bligh
2012-10-15 19:28 ` Eric Blake [this message]
2012-10-15 20:28 ` Alex Bligh
2012-10-23 16:41 ` Christoph Hellwig
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=507C63CB.7090006@redhat.com \
--to=eblake@redhat.com \
--cc=alex@alex.org.uk \
--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).