All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
	quintela@redhat.com, seabios@seabios.org,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] KVM call agenda for 2013-05-21
Date: Tue, 21 May 2013 20:52:51 +0300	[thread overview]
Message-ID: <20130521175251.GA6098@redhat.com> (raw)
In-Reply-To: <519BA372.7060406@suse.de>

On Tue, May 21, 2013 at 06:40:18PM +0200, Andreas Färber wrote:
> 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

Agree, I think mail works better for notifications.

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

WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
	quintela@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 20:52:51 +0300	[thread overview]
Message-ID: <20130521175251.GA6098@redhat.com> (raw)
In-Reply-To: <519BA372.7060406@suse.de>

On Tue, May 21, 2013 at 06:40:18PM +0200, Andreas Färber wrote:
> 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

Agree, I think mail works better for notifications.

> -- 
> 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 17:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 10:57 KVM call agenda for 2013-05-21 Juan Quintela
2013-05-20 10:57 ` [Qemu-devel] " Juan Quintela
2013-05-20 13:25 ` Michael S. Tsirkin
2013-05-20 13:25   ` [Qemu-devel] " Michael S. Tsirkin
2013-05-21 12:18   ` Anthony Liguori
2013-05-21 12:18     ` [Qemu-devel] " Anthony Liguori
2013-05-21 12:33     ` Michael S. Tsirkin
2013-05-21 12:33       ` [Qemu-devel] " Michael S. Tsirkin
2013-05-21 14:29       ` Anthony Liguori
2013-05-21 14:29         ` [Qemu-devel] " Anthony Liguori
2013-05-21 14:34         ` Juan Quintela
2013-05-21 14:34           ` [Qemu-devel] " Juan Quintela
2013-05-21 16:40           ` Andreas Färber
2013-05-21 16:40             ` Andreas Färber
2013-05-21 17:52             ` Michael S. Tsirkin [this message]
2013-05-21 17:52               ` Michael S. Tsirkin
2013-05-21 17:53         ` Michael S. Tsirkin
2013-05-21 17:53           ` [Qemu-devel] " Michael S. Tsirkin
2013-05-21 18:59           ` Anthony Liguori
2013-05-21 18:59             ` [Qemu-devel] " Anthony Liguori
2013-05-21 14:00 ` Juan Quintela
2013-05-21 14:00   ` [Qemu-devel] " 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=20130521175251.GA6098@redhat.com \
    --to=mst@redhat.com \
    --cc=afaerber@suse.de \
    --cc=kvm@vger.kernel.org \
    --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 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.