qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: quintela@redhat.com
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: KVM call agenda for Feb 1
Date: Mon, 31 Jan 2011 19:10:48 +0100	[thread overview]
Message-ID: <4D46FB28.9040801@siemens.com> (raw)
In-Reply-To: <m3hbcpgzm0.fsf@trasno.org>

On 2011-01-31 11:02, Juan Quintela wrote:
> 
> Please send in any agenda items you are interested incovering.
> 

 o KVM upstream merge: status, plans, coordination

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-01-31 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 10:02 [Qemu-devel] KVM call agenda for Feb 1 Juan Quintela
2011-01-31 18:10 ` Jan Kiszka [this message]
2011-01-31 21:39   ` [Qemu-devel] " Anthony Liguori
2011-02-01 12:40     ` Paolo Bonzini
2011-02-01 12:53     ` Luiz Capitulino
2011-02-01 12:56       ` Luiz Capitulino
2011-02-01 14:37         ` Alexander Graf
2011-02-01 15:05           ` Anthony Liguori
2011-02-01 15:27             ` Alexander Graf

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=4D46FB28.9040801@siemens.com \
    --to=jan.kiszka@siemens.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).