From: Avi Kivity <avi@redhat.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] Re: KVM Call agenda for July 13th
Date: Tue, 13 Jul 2010 10:40:40 +0300 [thread overview]
Message-ID: <4C3C1878.2060003@redhat.com> (raw)
In-Reply-To: <4C3C0E5C.50902@aurel32.net>
On 07/13/2010 09:57 AM, Aurelien Jarno wrote:
> Avi Kivity a écrit :
>
>> On 07/12/2010 05:57 PM, Juan Quintela wrote:
>>
>>> Please send in any agenda items you are interested in covering.
>>>
>>>
>>>
>> 0.12.n+1
>>
>>
> I won't be at the KVM call, but I can work on that in the next days.
>
> Basically the stable tree already contains a lot of fixes and we can do
> a call for patches for this release. One week should be enough, so that
> we can have the release at the end of next week (a few technical days
> are needed in addition).
>
Thanks.
I'd like to see more frequent stable releases, at least if the stable
branch contains fixes to user-reported bugs (or of course security or
data integrity fixes).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-07-13 7:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 14:57 [Qemu-devel] KVM Call agenda for July 13th Juan Quintela
2010-07-12 21:57 ` [Qemu-devel] " Chris Wright
2010-07-12 22:07 ` Anthony Liguori
2010-07-12 22:08 ` Anthony Liguori
2010-07-13 4:38 ` Avi Kivity
2010-07-13 14:03 ` Anthony Liguori
2010-07-16 22:13 ` Artyom Tarasenko
2010-07-13 4:37 ` Avi Kivity
2010-07-13 6:57 ` Aurelien Jarno
2010-07-13 7:40 ` Avi Kivity [this message]
2010-07-13 14:08 ` Luiz Capitulino
2010-07-13 15:03 ` Avi Kivity
2010-07-13 16:57 ` Anthony Liguori
2010-07-13 17:01 ` Avi Kivity
2010-07-13 17:19 ` Brian Jackson
2010-07-13 17:48 ` Avi Kivity
2010-07-15 18:43 ` Justin M. Forbes
2010-07-15 18:51 ` Aurelien Jarno
2010-07-15 18:54 ` Anthony Liguori
2010-07-13 6:31 ` 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=4C3C1878.2060003@redhat.com \
--to=avi@redhat.com \
--cc=aurelien@aurel32.net \
--cc=kvm@vger.kernel.org \
--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).