From: Avi Kivity <avi@redhat.com>
To: Brian Jackson <iggy@theiggy.com>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Re: KVM Call agenda for July 13th
Date: Tue, 13 Jul 2010 20:48:39 +0300 [thread overview]
Message-ID: <4C3CA6F7.10405@redhat.com> (raw)
In-Reply-To: <201007131219.21649.iggy@theiggy.com>
On 07/13/2010 08:19 PM, Brian Jackson wrote:
>
>> Yes. But in this context I'm interested in stable releases. We have
>> bugs reported, fixed, and the fix applied, yet the fixes are unreachable
>> to users.
>>
> Especially so since qemu-kvm 0.12-stable hasn't been merged with qemu
> basically since 0.12.4 came out. I was trying to help one of the Gentoo
> maintainers find post 0.12.4 patches the other day and had to point them to
> the upstream qemu stable tree.
>
An email should suffice to get things merged.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-07-13 17:49 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
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 [this message]
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=4C3CA6F7.10405@redhat.com \
--to=avi@redhat.com \
--cc=aurelien@aurel32.net \
--cc=iggy@theiggy.com \
--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).