From: Aurelien Jarno <aurelien@aurel32.net>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: KVM call agenda for Apr 27
Date: Tue, 27 Apr 2010 05:39:52 +0200 [thread overview]
Message-ID: <20100427033952.GA32748@hall.aurel32.net> (raw)
In-Reply-To: <20100426221558.328661e6@redhat.com>
On Mon, Apr 26, 2010 at 10:15:58PM -0300, Luiz Capitulino wrote:
> On Mon, 26 Apr 2010 12:51:08 -0500
> Anthony Liguori <anthony@codemonkey.ws> wrote:
>
> > On 04/26/2010 12:26 PM, Chris Wright wrote:
> > > Please send in any agenda items you are interested in covering.
> > >
> > > While I don't expect it to be the case this week, if we have a
> > > lack of agenda items I'll cancel the week's call.
> > >
> >
> > - qemu management interface (and libvirt)
> > - stable tree policy (push vs. pull and call for stable volunteers)
>
> What do you mean by push vs. pull?
>
> Anyway, Aurelien was working on a stable release last week, maybe
> he's interested in helping with the stables (or not :)).
>
I didn't find the time to do the stable release, but we should be very
close now.
I am interested to have stable releases, but if someone else want to
work on that, I am fine.
--
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: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: KVM call agenda for Apr 27
Date: Tue, 27 Apr 2010 05:39:52 +0200 [thread overview]
Message-ID: <20100427033952.GA32748@hall.aurel32.net> (raw)
In-Reply-To: <20100426221558.328661e6@redhat.com>
On Mon, Apr 26, 2010 at 10:15:58PM -0300, Luiz Capitulino wrote:
> On Mon, 26 Apr 2010 12:51:08 -0500
> Anthony Liguori <anthony@codemonkey.ws> wrote:
>
> > On 04/26/2010 12:26 PM, Chris Wright wrote:
> > > Please send in any agenda items you are interested in covering.
> > >
> > > While I don't expect it to be the case this week, if we have a
> > > lack of agenda items I'll cancel the week's call.
> > >
> >
> > - qemu management interface (and libvirt)
> > - stable tree policy (push vs. pull and call for stable volunteers)
>
> What do you mean by push vs. pull?
>
> Anyway, Aurelien was working on a stable release last week, maybe
> he's interested in helping with the stables (or not :)).
>
I didn't find the time to do the stable release, but we should be very
close now.
I am interested to have stable releases, but if someone else want to
work on that, I am fine.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2010-04-27 3:40 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 17:26 KVM call agenda for Apr 27 Chris Wright
2010-04-26 17:26 ` [Qemu-devel] " Chris Wright
2010-04-26 17:51 ` Anthony Liguori
2010-04-26 17:51 ` [Qemu-devel] " Anthony Liguori
2010-04-26 22:12 ` Chris Wright
2010-04-26 22:12 ` [Qemu-devel] " Chris Wright
2010-04-26 22:36 ` Anthony Liguori
2010-04-26 22:36 ` [Qemu-devel] " Anthony Liguori
2010-04-27 8:14 ` Avi Kivity
2010-04-27 8:14 ` [Qemu-devel] " Avi Kivity
2010-04-27 8:48 ` Dor Laor
2010-04-27 8:48 ` [Qemu-devel] " Dor Laor
2010-04-27 8:56 ` Avi Kivity
2010-04-27 8:56 ` [Qemu-devel] " Avi Kivity
2010-04-27 9:08 ` Dor Laor
2010-04-27 9:08 ` [Qemu-devel] " Dor Laor
2010-04-27 9:22 ` Avi Kivity
2010-04-27 9:22 ` [Qemu-devel] " Avi Kivity
2010-04-27 9:32 ` Dor Laor
2010-04-27 9:32 ` [Qemu-devel] " Dor Laor
2010-04-27 9:41 ` Kevin Wolf
2010-04-27 9:41 ` [Qemu-devel] " Kevin Wolf
2010-04-27 13:15 ` Anthony Liguori
2010-04-27 13:15 ` [Qemu-devel] " Anthony Liguori
2010-04-27 9:16 ` Kevin Wolf
2010-04-27 9:16 ` [Qemu-devel] " Kevin Wolf
2010-04-27 9:28 ` Avi Kivity
2010-04-27 9:28 ` [Qemu-devel] " Avi Kivity
2010-04-27 13:03 ` Anthony Liguori
2010-04-27 13:03 ` [Qemu-devel] " Anthony Liguori
2010-04-27 13:08 ` Avi Kivity
2010-04-27 13:08 ` [Qemu-devel] " Avi Kivity
2010-04-27 13:11 ` Daniel P. Berrange
2010-04-27 13:11 ` [Qemu-devel] " Daniel P. Berrange
2010-04-27 13:15 ` Gleb Natapov
2010-04-27 13:15 ` [Qemu-devel] " Gleb Natapov
2010-04-27 13:38 ` Daniel P. Berrange
2010-04-27 13:38 ` [Qemu-devel] " Daniel P. Berrange
2010-04-27 14:10 ` Gleb Natapov
2010-04-27 14:10 ` [Qemu-devel] " Gleb Natapov
2010-04-27 8:53 ` Kevin Wolf
2010-04-27 13:10 ` Anthony Liguori
2010-04-27 13:18 ` Kevin Wolf
2010-04-27 13:21 ` Anthony Liguori
2010-04-27 13:42 ` Kevin Wolf
2010-04-27 13:48 ` Anthony Liguori
2010-04-27 13:58 ` Kevin Wolf
2010-04-27 14:01 ` Anthony Liguori
2010-04-27 11:11 ` Gleb Natapov
2010-04-27 11:11 ` [Qemu-devel] " Gleb Natapov
2010-04-27 13:00 ` Anthony Liguori
2010-04-27 13:00 ` [Qemu-devel] " Anthony Liguori
2010-04-27 13:05 ` Gleb Natapov
2010-04-27 13:05 ` [Qemu-devel] " Gleb Natapov
2010-04-27 13:19 ` Anthony Liguori
2010-04-27 13:19 ` [Qemu-devel] " Anthony Liguori
2010-04-27 13:29 ` Gleb Natapov
2010-04-27 13:29 ` [Qemu-devel] " Gleb Natapov
2010-04-27 1:15 ` Luiz Capitulino
2010-04-27 1:15 ` Luiz Capitulino
2010-04-27 3:39 ` Aurelien Jarno [this message]
2010-04-27 3:39 ` Aurelien Jarno
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=20100427033952.GA32748@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=anthony@codemonkey.ws \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@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.