From: Anthony Liguori <anthony@codemonkey.ws>
To: Markus Armbruster <armbru@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 00/10] Make some devices optional
Date: Fri, 04 Feb 2011 11:24:33 -0600 [thread overview]
Message-ID: <4D4C3651.4020609@codemonkey.ws> (raw)
In-Reply-To: <m3ipx0gr8k.fsf@blackfin.pond.sub.org>
On 02/04/2011 02:04 AM, Markus Armbruster wrote:
> Blue Swirl<blauwirbel@gmail.com> writes:
>
>
>> Disabling some devices from build is a frequently requested feature.
>> Provide means to disable vmware_vga, vmmouse and HPET.
>>
> Long patch series without proper threading are a PITA to review.
> git-send-email adds the necessary headers automatically. Could you try
> using it? Thanks.
>
Would be nice for someone to put up a quick wiki page with a short
tutorial on git-send-email (under a SubmittingPatches) page.
Regards,
Anthony Liguori
prev parent reply other threads:[~2011-02-04 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 20:58 [Qemu-devel] [PATCH v2 00/10] Make some devices optional Blue Swirl
2011-02-04 8:04 ` Markus Armbruster
2011-02-04 17:24 ` Anthony Liguori [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=4D4C3651.4020609@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=blauwirbel@gmail.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).