qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: quintela@redhat.com
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	seabios@seabios.org,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>,
	kevin@koconnor.net, ddutile@redhat.com,
	Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] KVM call agenda for 2013-05-21
Date: Tue, 21 May 2013 18:40:18 +0200	[thread overview]
Message-ID: <519BA372.7060406@suse.de> (raw)
In-Reply-To: <87txlwqu55.fsf@elfo.elfo>

Am 21.05.2013 16:34, schrieb Juan Quintela:
> Anthony Liguori <anthony@codemonkey.ws> wrote:
>> Maybe we could use a wiki page to setup a rolling agenda?
> 
> I think this could be easier for everybody involved.
> 
> Especially because you just look if there is anything to discuss?

On the other hand, the Wiki doesn't send out notifications on change.
So if we looked at a Wiki page five minutes before the call to check if
there are topics, it's too late to read through discussions or papers.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-05-21 16:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 10:57 [Qemu-devel] KVM call agenda for 2013-05-21 Juan Quintela
2013-05-20 13:25 ` Michael S. Tsirkin
2013-05-21 12:18   ` Anthony Liguori
2013-05-21 12:33     ` Michael S. Tsirkin
2013-05-21 14:29       ` Anthony Liguori
2013-05-21 14:34         ` Juan Quintela
2013-05-21 16:40           ` Andreas Färber [this message]
2013-05-21 17:52             ` Michael S. Tsirkin
2013-05-21 17:53         ` Michael S. Tsirkin
2013-05-21 18:59           ` Anthony Liguori
2013-05-21 14:00 ` Juan Quintela

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=519BA372.7060406@suse.de \
    --to=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=ddutile@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=seabios@seabios.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 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).