qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: quintela@redhat.com
Cc: corey Bryant <coreyb@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org,
	KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call agenda for June, Tuesday 15th
Date: Mon, 14 May 2012 10:42:06 -0500	[thread overview]
Message-ID: <4FB127CE.1050706@codemonkey.ws> (raw)
In-Reply-To: <87vcjz0wal.fsf@elfo.elfo>

On 05/14/2012 07:41 AM, Juan Quintela wrote:
>
> Hi
>
> Please send in any agenda items you are interested in covering.

-open-fd-hook proposal

The discussion seems to have tapered out without a consensus.

Regards,

Anthony Liguori

>
> Thanks, Juan.
>

  reply	other threads:[~2012-05-14 15:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 12:41 [Qemu-devel] KVM call agenda for June, Tuesday 15th Juan Quintela
2012-05-14 15:42 ` Anthony Liguori [this message]
2012-05-14 16:24   ` Paolo Bonzini
2012-05-15  8:51   ` Kevin Wolf
2012-05-15 13:44     ` Anthony Liguori
2012-05-15 13:54       ` Daniel P. Berrange

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=4FB127CE.1050706@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=coreyb@linux.vnet.ibm.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).