From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kwolf@redhat.com, stefanha@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/1] qemu-img.c: Clean up handling of image size in img_create()
Date: Wed, 15 Dec 2010 17:56:12 +0100 [thread overview]
Message-ID: <4D08F32C.1090503@redhat.com> (raw)
In-Reply-To: <m34oafasoy.fsf@blackfin.pond.sub.org>
On 12/15/10 17:47, Markus Armbruster wrote:
> Jes.Sorensen@redhat.com writes:
>
>> From: Jes Sorensen <Jes.Sorensen@redhat.com>
>>
>> This cleans up the handling of image size in img_create() by parsing
>> the value early, and then only setting it once if a value has been
>> added as the last argument to the command line.
>>
>> Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
>> ---
>> qemu-img.c | 14 ++++++++------
>> 1 files changed, 8 insertions(+), 6 deletions(-)
>>
>
> Patch conflicts with commit c2abccec.
ARGH :(
> This switches parsing of the size argument from parse_option_size() (via
> set_option_parameter()) to strtosz(). I'm fine with that, but:
>
> * Before:
>
> $ qemu-img create xxx xxx
> Parameter 'size' expects a size
> You may use k, M, G or T suffixes for kilobytes, megabytes, gigabytes and terabytes.
> qemu-img: Image creation needs a size parameter
>
> * After:
>
> $ qemu-img create xxx xxx
> qemu-img: Image creation needs a size parameter
>
> Intentional?
This was addressed in the later revision when I introduced strtosz_suffix()
Cheers,
Jes
next prev parent reply other threads:[~2010-12-15 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 9:13 [Qemu-devel] [PATCH v2 1/1] qemu-img.c: Clean up handling of image size in img_create() Jes.Sorensen
2010-12-15 16:47 ` Markus Armbruster
2010-12-15 16:56 ` Jes Sorensen [this message]
2010-12-15 17:23 ` Markus Armbruster
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=4D08F32C.1090503@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).