From: Alex Bligh <alex@alex.org.uk>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, Alex Bligh <alex@alex.org.uk>
Subject: Re: [Qemu-devel] [PATCH] qemu-img rebase: allow backing file to be specified as '-'
Date: Mon, 15 Oct 2012 21:28:55 +0100 [thread overview]
Message-ID: <3C3D5F4A66E64EE2BCDB750F@nimrod.local> (raw)
In-Reply-To: <507C63CB.7090006@redhat.com>
Eric,
--On 15 October 2012 13:28:11 -0600 Eric Blake <eblake@redhat.com> wrote:
> Missing a Signed-off-by; as such, it cannot be taken as is.
New patch sent under separate cover with Signed-Off-By: line.
>> @@ -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?).
I'm totally confused by the spacing artifact. The new patch was generated
with git-format-patch and git-send-email, and never touched a mailer (just
in case), and also shows under the same circumstances. It doesn't show the
bizarre indent in Mulberry, but does in Apple Mail. The patch applies
cleanly with git-am and doesn't moan about whitespace, and as far as I can
tell the resultant whitespace in the file is correct (i.e. matches the
preceding and subsequent lines).
> Also, most of qemu uses spaces on both sides of '='.
Fixed.
> But the overall idea looks nice.
Thanks
--
Alex Bligh
next prev parent reply other threads:[~2012-10-15 20:29 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
2012-10-15 20:28 ` Alex Bligh [this message]
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=3C3D5F4A66E64EE2BCDB750F@nimrod.local \
--to=alex@alex.org.uk \
--cc=eblake@redhat.com \
--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).