From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>
Cc: qemu list <qemu-devel@nongnu.org>
Subject: Re: KVM call agenfda for 2014-04-01
Date: Tue, 01 Apr 2014 14:39:49 +0200 [thread overview]
Message-ID: <87zjk5b4ve.fsf@elfo.mitica> (raw)
In-Reply-To: <87mwg6ejn8.fsf@elfo.mitica> (Juan Quintela's message of "Mon, 31 Mar 2014 12:40:11 +0200")
Juan Quintela <quintela@redhat.com> wrote:
> Hi
>
> Please, send any topic that you are interested in covering.
>
> Thanks, Juan.
>
> Call details:
>
> 10:00 AM to 11:00 AM EDT
> Every two weeks
Time clarification. This time was wrong, it is 1h early.
15:00 CEST
13:00 UTC
09:00 EDT
Sorry for the inconvenience (I copy & paste from and old email, and did
it wrong.)
Later, Juan.
>
> If you need phone number details, contact me privately.
WARNING: multiple messages have this Message-ID (diff)
From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>
Cc: qemu list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] KVM call agenfda for 2014-04-01
Date: Tue, 01 Apr 2014 14:39:49 +0200 [thread overview]
Message-ID: <87zjk5b4ve.fsf@elfo.mitica> (raw)
In-Reply-To: <87mwg6ejn8.fsf@elfo.mitica> (Juan Quintela's message of "Mon, 31 Mar 2014 12:40:11 +0200")
Juan Quintela <quintela@redhat.com> wrote:
> Hi
>
> Please, send any topic that you are interested in covering.
>
> Thanks, Juan.
>
> Call details:
>
> 10:00 AM to 11:00 AM EDT
> Every two weeks
Time clarification. This time was wrong, it is 1h early.
15:00 CEST
13:00 UTC
09:00 EDT
Sorry for the inconvenience (I copy & paste from and old email, and did
it wrong.)
Later, Juan.
>
> If you need phone number details, contact me privately.
next prev parent reply other threads:[~2014-04-01 12:39 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 10:40 KVM call agenfda for 2014-04-01 Juan Quintela
2014-03-31 10:40 ` [Qemu-devel] " Juan Quintela
2014-03-31 10:51 ` [Qemu-devel] KVM call agenda " Andreas Färber
2014-03-31 10:51 ` Andreas Färber
2014-03-31 12:07 ` Stefan Hajnoczi
2014-03-31 12:07 ` Stefan Hajnoczi
2014-03-31 13:21 ` Christian Borntraeger
2014-03-31 13:21 ` Christian Borntraeger
2014-03-31 13:25 ` Peter Maydell
2014-03-31 13:25 ` Peter Maydell
2014-03-31 14:01 ` Anthony Liguori
2014-03-31 14:01 ` Anthony Liguori
2014-03-31 14:28 ` Paolo Bonzini
2014-03-31 14:28 ` Paolo Bonzini
2014-03-31 14:32 ` Peter Maydell
2014-03-31 14:32 ` Peter Maydell
2014-03-31 14:46 ` Andreas Färber
2014-03-31 14:46 ` Andreas Färber
2014-03-31 15:42 ` Anthony Liguori
2014-03-31 15:42 ` Anthony Liguori
2014-03-31 16:58 ` Markus Armbruster
2014-03-31 16:58 ` Markus Armbruster
2014-03-31 19:57 ` Michael Roth
2014-03-31 19:57 ` Michael Roth
2014-04-01 8:16 ` Peter Maydell
2014-04-01 8:16 ` [Qemu-devel] " Peter Maydell
2014-04-01 12:39 ` Juan Quintela [this message]
2014-04-01 12:39 ` [Qemu-devel] KVM call agenfda " Juan Quintela
2014-04-10 15:49 ` Alexander Graf
2014-04-10 15:49 ` Alexander Graf
2014-04-10 15:52 ` Peter Maydell
2014-04-10 15:52 ` Peter Maydell
2014-04-10 15:57 ` Alexander Graf
2014-04-10 15:57 ` Alexander Graf
2014-04-10 16:16 ` Stuart Yoder
2014-04-10 16:16 ` Stuart Yoder
2014-04-11 7:46 ` Markus Armbruster
2014-04-11 7:46 ` Markus Armbruster
2014-04-11 9:17 ` Alexander Graf
2014-04-11 9:17 ` Alexander Graf
2014-04-15 13:10 ` Andreas Färber
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=87zjk5b4ve.fsf@elfo.mitica \
--to=quintela@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.