From: Frederic Konrad <fred.konrad@greensocs.com>
To: quintela@redhat.com
Cc: Orit Wasserman <owasserm@redhat.com>,
Mark Burton <mark.burton@greensocs.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] KVM call agenda for 2013-07-16
Date: Mon, 22 Jul 2013 17:05:25 +0200 [thread overview]
Message-ID: <51ED4A35.30707@greensocs.com> (raw)
In-Reply-To: <871u762ky1.fsf@elfo.elfo>
On 10/07/2013 22:56, Juan Quintela wrote:
> Hi
>
> Please, send any topic that you are interested in covering.
>
> Thanks, Juan.
>
> PD. If you want to attend and you don't have the call details,
> contact me.
>
Hi Juan,
Is there any call tomorrow?
If it's the case, we would like to discuss about IO replay topic which
is involved
in our reverse execution project and fault tolerance.
Thanks,
Fred.
prev parent reply other threads:[~2013-07-22 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 20:56 [Qemu-devel] KVM call agenda for 2013-07-16 Juan Quintela
2013-07-22 15:05 ` Frederic Konrad [this message]
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=51ED4A35.30707@greensocs.com \
--to=fred.konrad@greensocs.com \
--cc=kvm@vger.kernel.org \
--cc=mark.burton@greensocs.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--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).