From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: New kvm-related qemu patch queue
Date: Sun, 17 Jan 2010 14:51:26 +0200 [thread overview]
Message-ID: <4B5307CE.3000706@redhat.com> (raw)
In-Reply-To: <4B4B4404.9090304@codemonkey.ws>
On 01/11/2010 05:30 PM, Anthony Liguori wrote:
> On 01/10/2010 06:02 AM, Avi Kivity wrote:
>> In order to improve qemu.git kvm integration quality wrt performance,
>> features, and reliability Marcelo and I will begin to maintain a
>> patch queue based on qemu.git containing kvm-related patches. We
>> will review and apply patches to this queue, test them using the same
>> test suite that is used for qemu-kvm.git, and regularly submit them
>> for inclusion in qemu.git, mimicking the relationship between kvm.git
>> and Linus' linux-2.6.git.
>
> Thanks for setting this up Avi!
>
> I just want to stress that everyone continue CC'ing qemu-devel on all
> KVM patches. Even if the patch is qemu-kvm specific for the moment, I
> think it's important for qemu-devel to be exposed to the refactoring
> work.
>
> It might be good to prefix qemu-kvm.git patches in some manner to make
> it clear which repository they belong to.
[patch kvm] - qemu-kvm.git uq/master
[patch qemu-kvm] - qemu-kvm.git master
[patch kvm stable-0.12] - qemu-kvm uq/stable-0.12
etc.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-01-17 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 12:02 [Qemu-devel] New kvm-related qemu patch queue Avi Kivity
2010-01-10 14:28 ` [Qemu-devel] " Gleb Natapov
2010-01-10 14:30 ` Avi Kivity
2010-01-10 14:49 ` Gleb Natapov
2010-01-10 14:52 ` Avi Kivity
2010-01-11 7:51 ` Gleb Natapov
2010-01-11 15:30 ` Anthony Liguori
2010-01-17 12:51 ` Avi Kivity [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=4B5307CE.3000706@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--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).