From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] The development tree is now open!
Date: Tue, 05 Jun 2012 16:07:33 +0300 [thread overview]
Message-ID: <4FCE0495.7010505@redhat.com> (raw)
In-Reply-To: <4FCB9977.60504@web.de>
On 06/03/2012 08:05 PM, Jan Kiszka wrote:
> On 2012-06-02 11:53, Anthony Liguori wrote:
>> Let your PATCHes, PULLs, RFCs, and RFTs start flowing. I'll start
>> applying pull requests on Monday or perhaps earlier if I can find the time.
>>
>> For submaintainers, if you have a very large queue (> 50 patches),
>> please split your pulls into multiple pull requests of reasonable size
>> (~50) and submit them spaced out a week at a time. If you have a lot of
>> safe/trivial patches, of course use your best judgement.
>
> Would be great if [1] could be merged quickly as quite some work on
> qemu-kvm depends on its back-merge.
>
> Hopefully, we will be able to finally close the feature gap between
> qemu-kvm and upstream with 1.2.
>
Note, I am holding off on the qemu-kvm-1.1 release pending investigation
of the qcow2/ide bug that Yongjie Ren discovered. But if it's holding
you off, I can branch 1.1 now and merge this early to master.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-06-05 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 9:53 [Qemu-devel] The development tree is now open! Anthony Liguori
2012-06-03 17:05 ` Jan Kiszka
2012-06-05 13:07 ` Avi Kivity [this message]
2012-06-05 13:19 ` Jan Kiszka
2012-06-06 11:37 ` Avi Kivity
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=4FCE0495.7010505@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@web.de \
--cc=mtosatti@redhat.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 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.