From: Fam Zheng <famz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Mike Day <ncmike@ncultra.org>,
cornelia.huck@de.ibm.com, qemu-devel@nongnu.org,
stefanha@redhat.com, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH] qemu-img: sort block formats in help message
Date: Wed, 14 May 2014 16:09:14 +0800 [thread overview]
Message-ID: <20140514080914.GG1856@T430.nay.redhat.com> (raw)
In-Reply-To: <20140514075046.GC3610@noname.redhat.com>
On Wed, 05/14 09:50, Kevin Wolf wrote:
> Am 13.05.2014 um 18:07 hat Mike Day geschrieben:
> > The help message for qemu-img lists the supported block formats, of
> > which there are 27 as of version 2.0.50. The formats are printed in
> > the order of their driver's position in a linked list, which appears
> > random. This patch prints the formats in sorted order, making it
> > easier to read and to find a specific format in the list.
> >
> > [Added suggestions from Fam Zheng <famz@redhat.com> to declare variables
> > at the top of the scope in help() and to omit explicit cast for void*
> > opaque.
> > --Stefan]
> >
> > [Removed call to g_sequence_lookup because it breaks the build on
> > machines with glib < 2.28.
> > --Mike]
> >
> > Signed-off-by: Mike Day <ncmike@ncultra.org>
> > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>
> What happened here? This patch seems to be already applied, and you
> included Stefan's SoB as well.
>
Mike, please fix on top of current master, instead of squashing the removing of
g_sequence_lookup into your already merged patch.
Fam
next prev parent reply other threads:[~2014-05-14 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 16:07 [Qemu-devel] [PATCH] qemu-img: sort block formats in help message Mike Day
2014-05-13 17:48 ` Markus Armbruster
2014-05-14 7:50 ` Kevin Wolf
2014-05-14 8:09 ` Fam Zheng [this message]
2014-05-14 13:02 ` Stefan Hajnoczi
2014-05-14 13:28 ` Mike Day
-- strict thread matches above, loose matches on Subject: below --
2014-05-02 13:11 Mike Day
2014-05-05 13:42 ` Stefan Hajnoczi
2014-05-05 16:02 ` Mike Day
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=20140514080914.GG1856@T430.nay.redhat.com \
--to=famz@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=kwolf@redhat.com \
--cc=ncmike@ncultra.org \
--cc=peter.maydell@linaro.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).