From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>, kvm-devel <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] KVM Call agenda for July 6th
Date: Tue, 06 Jul 2010 17:27:59 +0200 [thread overview]
Message-ID: <4C334B7F.7070108@redhat.com> (raw)
In-Reply-To: <m3ocekzlh9.fsf@blackfin.pond.sub.org>
Am 06.07.2010 17:19, schrieb Markus Armbruster:
> Kevin Wolf <kwolf@redhat.com> writes:
>
>> Am 06.07.2010 15:53, schrieb Anthony Liguori:
>>> On 07/06/2010 08:37 AM, Kevin Wolf wrote:
>>>> Am 06.07.2010 15:26, schrieb Anthony Liguori:
>>>>
>>>>> On 07/05/2010 09:05 AM, Luiz Capitulino wrote:
>>>>>
>>>>>> On Mon, 05 Jul 2010 14:45:23 +0200
>>>>>> Juan Quintela<quintela@redhat.com> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Please send in any agenda items you are interested in covering.
>>>>>>>
>>>>>>>
>>>>>> - 0.13 release
>>>>>>
>>>>>>
>>>>> I was hoping to do -rc0 before the holiday but that didn't happen so I'm
>>>>> working on it now. Figure release is ~1 week from -rc0.
>>>>>
>>>> What does this mean for patches that should go into 0.13 and aren't
>>>> strictly bug fixes? When should the pull request be sent latest?
>>>>
>>>
>>> Last week?
>>
>> Sure, but it didn't happen then and things have moved forward.
>>
>>> I'd really like to put out -rc0 today and I'm trying to free up time to
>>> get through the backlog of patches to make that happen. I just pushed
>>> your latest pull. If you've got another pull request ready send it
>>> now. But I can't promise that I'll take anything that hasn't already
>>> shown up.
>>
>> I'm just reviewing and merging v2 of Markus' block fixes/cleanups and
>> I'm considering the Sheepdog block driver (which seems to have had
>> enough iterations and doesn't touch a single line of code outside its
>> own file).
>
> Any chance to get the next series (Split ide-drive and scsi-disk qdevs,
> and more) as well? 1-3/8 are bug fixes, and 4/8 removes unreliable
> information from info block; wanted in .13. 5-8/8 could be punted to
> .14.
If it's purely bug fixes, I think we can still take it after -rc0.
Kevin
next prev parent reply other threads:[~2010-07-06 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 12:45 [Qemu-devel] KVM Call agenda for July 6th Juan Quintela
2010-07-05 14:05 ` Luiz Capitulino
2010-07-06 4:52 ` Alex Williamson
2010-07-06 13:26 ` Anthony Liguori
2010-07-06 13:53 ` Alex Williamson
2010-07-06 13:26 ` Anthony Liguori
2010-07-06 13:37 ` Kevin Wolf
2010-07-06 13:53 ` Anthony Liguori
2010-07-06 14:04 ` Kevin Wolf
2010-07-06 15:19 ` Markus Armbruster
2010-07-06 15:27 ` Kevin Wolf [this message]
2010-07-06 15:33 ` Anthony Liguori
2010-07-06 13:28 ` [Qemu-devel] " Anthony Liguori
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=4C334B7F.7070108@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).