All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: KVM call agenda for Jan 25
Date: Tue, 25 Jan 2011 12:02:44 -0200	[thread overview]
Message-ID: <20110125120244.5b18863d@doriath> (raw)
In-Reply-To: <20110125115727.5f2b495e@doriath>

On Tue, 25 Jan 2011 11:57:27 -0200
Luiz Capitulino <lcapitulino@redhat.com> wrote:

> On Mon, 24 Jan 2011 16:06:34 -0600
> Anthony Liguori <anthony@codemonkey.ws> wrote:
> 
> > On 01/24/2011 07:25 AM, Chris Wright wrote:
> > > Please send in any agenda items you are interested in covering.
> > >    
> > 
> > - coroutines for the block layer
> > - glib everywhere
> 
> - Let's start planning our next release in advance, here's a simple example:
> 
>   http://wiki.qemu.org/Planning/0.15-example

Forgot:

 - Google summer of code 2011 is on, are we interested? (note: I just saw the
   news, I don't have any information yet)
> 
> > 
> > Regards,
> > 
> > Anthony Liguori
> > 
> > > thanks,
> > > -chris
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > >    
> > 
> > 
> 
> 


  reply	other threads:[~2011-01-25 14:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 13:25 KVM call agenda for Jan 25 Chris Wright
2011-01-24 13:25 ` [Qemu-devel] " Chris Wright
2011-01-24 22:06 ` Anthony Liguori
2011-01-24 22:06   ` [Qemu-devel] " Anthony Liguori
2011-01-25 13:57   ` Luiz Capitulino
2011-01-25 14:02     ` Luiz Capitulino [this message]
2011-01-25 14:13       ` Stefan Hajnoczi
2011-01-25 14:13         ` Stefan Hajnoczi
2011-01-29 10:50         ` Dushyant Bansal
2011-01-29 13:16           ` Stefan Hajnoczi
2011-02-25 17:42           ` Dushyant Bansal
2011-02-26 14:05             ` Stefan Hajnoczi
2011-02-26 21:50               ` Dushyant Bansal
2011-02-27 10:49                 ` Stefan Hajnoczi
2011-02-28  7:36                   ` Markus Armbruster
2011-02-28 20:41                   ` Dushyant Bansal
2011-03-01  9:40                     ` Stefan Hajnoczi
2011-03-14 15:13                       ` Dushyant Bansal
2011-03-15 10:27                         ` Kevin Wolf
2011-03-16 14:17                           ` Dushyant Bansal
2011-03-16 17:47                           ` Stefan Hajnoczi
2011-03-17 10:07                             ` Kevin Wolf
2011-03-26 21:56                               ` Dushyant Bansal
2011-03-28 10:26                                 ` Kevin Wolf
2011-01-25 14:11     ` Aurelien Jarno
2011-01-25 14:11       ` Aurelien Jarno
2011-01-25 14:27       ` Anthony Liguori
2011-01-25 14:27         ` Anthony Liguori
2011-01-25 14:42       ` Kevin Wolf
2011-01-25 14:42         ` Kevin Wolf
2011-01-25 15:29         ` Aurelien Jarno
2011-01-25 14:26   ` Avi Kivity
2011-01-25 14:26     ` [Qemu-devel] " Avi Kivity
2011-01-25 14:35     ` Stefan Hajnoczi
2011-01-25 14:35       ` [Qemu-devel] " Stefan Hajnoczi
2011-01-26  9:58       ` Avi Kivity
2011-01-26  9:58         ` [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=20110125120244.5b18863d@doriath \
    --to=lcapitulino@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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.