From: Aurelien Jarno <aurelien@aurel32.net>
To: "Justin M. Forbes" <jmforbes@linuxtx.org>
Cc: Brian Jackson <iggy@theiggy.com>, kvm-devel <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: KVM Call agenda for July 13th
Date: Thu, 15 Jul 2010 20:51:55 +0200 [thread overview]
Message-ID: <20100715185155.GU18814@hall.aurel32.net> (raw)
In-Reply-To: <20100715184328.GA16484@linuxtx.org>
On Thu, Jul 15, 2010 at 01:43:28PM -0500, Justin M. Forbes wrote:
> On Tue, Jul 13, 2010 at 12:19:21PM -0500, Brian Jackson wrote:
> > On Tuesday, July 13, 2010 12:01:22 pm Avi Kivity wrote:
> > > On 07/13/2010 07:57 PM, Anthony Liguori wrote:
> > > >> 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).
> > > >
> > > > Would you like to see more frequent stable releases or more frequent
> > > > master releases?
> > >
> > > 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.
>
> I have offered to take care of this, but so far I do not have commit
> access.
>
You don't necessarily need commit access for that. Just create your own
tree with backported patches, and then send a stable pull request to
the mailing list.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
WARNING: multiple messages have this Message-ID (diff)
From: Aurelien Jarno <aurelien@aurel32.net>
To: "Justin M. Forbes" <jmforbes@linuxtx.org>
Cc: Brian Jackson <iggy@theiggy.com>, Avi Kivity <avi@redhat.com>,
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: Thu, 15 Jul 2010 20:51:55 +0200 [thread overview]
Message-ID: <20100715185155.GU18814@hall.aurel32.net> (raw)
In-Reply-To: <20100715184328.GA16484@linuxtx.org>
On Thu, Jul 15, 2010 at 01:43:28PM -0500, Justin M. Forbes wrote:
> On Tue, Jul 13, 2010 at 12:19:21PM -0500, Brian Jackson wrote:
> > On Tuesday, July 13, 2010 12:01:22 pm Avi Kivity wrote:
> > > On 07/13/2010 07:57 PM, Anthony Liguori wrote:
> > > >> 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).
> > > >
> > > > Would you like to see more frequent stable releases or more frequent
> > > > master releases?
> > >
> > > 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.
>
> I have offered to take care of this, but so far I do not have commit
> access.
>
You don't necessarily need commit access for that. Just create your own
tree with backported patches, and then send a stable pull request to
the mailing list.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2010-07-15 18:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 14:57 KVM Call agenda for July 13th Juan Quintela
2010-07-12 14:57 ` [Qemu-devel] " Juan Quintela
2010-07-12 21:57 ` Chris Wright
2010-07-12 21:57 ` [Qemu-devel] " Chris Wright
2010-07-12 22:07 ` Anthony Liguori
2010-07-12 22:07 ` [Qemu-devel] " Anthony Liguori
2010-07-12 22:08 ` Anthony Liguori
2010-07-12 22:08 ` [Qemu-devel] " Anthony Liguori
2010-07-13 4:38 ` Avi Kivity
2010-07-13 4:38 ` [Qemu-devel] " Avi Kivity
2010-07-13 14:03 ` Anthony Liguori
2010-07-13 14:03 ` [Qemu-devel] " Anthony Liguori
2010-07-16 22:13 ` Artyom Tarasenko
2010-07-13 4:37 ` Avi Kivity
2010-07-13 4:37 ` [Qemu-devel] " Avi Kivity
2010-07-13 6:57 ` Aurelien Jarno
2010-07-13 6:57 ` Aurelien Jarno
2010-07-13 7:40 ` Avi Kivity
2010-07-13 7:40 ` Avi Kivity
2010-07-13 14:08 ` Luiz Capitulino
2010-07-13 14:08 ` Luiz Capitulino
2010-07-13 15:03 ` Avi Kivity
2010-07-13 15:03 ` Avi Kivity
2010-07-13 16:57 ` Anthony Liguori
2010-07-13 16:57 ` Anthony Liguori
2010-07-13 17:01 ` Avi Kivity
2010-07-13 17:01 ` Avi Kivity
2010-07-13 17:19 ` Brian Jackson
2010-07-13 17:19 ` Brian Jackson
2010-07-13 17:48 ` Avi Kivity
2010-07-13 17:48 ` Avi Kivity
2010-07-15 18:43 ` Justin M. Forbes
2010-07-15 18:43 ` Justin M. Forbes
2010-07-15 18:51 ` Aurelien Jarno [this message]
2010-07-15 18:51 ` Aurelien Jarno
2010-07-15 18:54 ` Anthony Liguori
2010-07-15 18:54 ` Anthony Liguori
2010-07-13 6:31 ` Avi Kivity
2010-07-13 6:31 ` [Qemu-devel] " 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=20100715185155.GU18814@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=avi@redhat.com \
--cc=iggy@theiggy.com \
--cc=jmforbes@linuxtx.org \
--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 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.