From: Markus Armbruster <armbru@redhat.com>
To: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Cc: kwolf@redhat.com, wdongxu@cn.ibm.com, qemu-devel@nongnu.org,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH V13 0/6] replace QEMUOptionParameter with QemuOpts parser
Date: Mon, 06 May 2013 14:26:30 +0200 [thread overview]
Message-ID: <87obcol2fd.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <1365575111-4476-1-git-send-email-wdongxu@linux.vnet.ibm.com> (Dong Xu Wang's message of "Wed, 10 Apr 2013 14:25:05 +0800")
Dong Xu Wang <wdongxu@linux.vnet.ibm.com> writes:
> These patches will replace QEMUOptionParameter with QemuOpts. Change logs
> please go to each patch's commit message.
I reviewed 1-4/6 for now. I'm sorry it has taken me so long. Let's
discuss my findings before I continue with 5/6, because that one's
*big*.
prev parent reply other threads:[~2013-05-06 12:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 6:25 [Qemu-devel] [PATCH V13 0/6] replace QEMUOptionParameter with QemuOpts parser Dong Xu Wang
2013-04-10 6:25 ` [Qemu-devel] [PATCH V13 1/6] add def_value_str in QemuOptDesc struct and rewrite qemu_opts_print Dong Xu Wang
2013-05-06 12:16 ` Markus Armbruster
2013-04-10 6:25 ` [Qemu-devel] [PATCH V13 2/6] avoid duplication of default value in QemuOpts Dong Xu Wang
2013-05-06 11:54 ` Markus Armbruster
2013-04-10 6:25 ` [Qemu-devel] [PATCH V13 3/6] Create four QemuOptsList related functions Dong Xu Wang
2013-04-10 6:25 ` [Qemu-devel] [PATCH V13 4/6] create some QemuOpts functons Dong Xu Wang
2013-05-06 12:20 ` Markus Armbruster
2013-05-07 5:19 ` Dong Xu Wang
2013-05-07 7:38 ` Markus Armbruster
2013-05-07 7:53 ` Dong Xu Wang
2013-04-10 6:25 ` [Qemu-devel] [PATCH V13 5/6] Use QemuOpts support in block layer Dong Xu Wang
2013-04-10 6:25 ` [Qemu-devel] [PATCH V13 6/6] remove QEMUOptionParameter related functions and struct Dong Xu Wang
2013-04-22 2:20 ` [Qemu-devel] [PATCH V13 0/6] replace QEMUOptionParameter with QemuOpts parser Dong Xu Wang
2013-04-22 8:18 ` Markus Armbruster
2013-05-06 12:26 ` Markus Armbruster [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=87obcol2fd.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wdongxu@cn.ibm.com \
--cc=wdongxu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.