From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] KVM call agenda for 2013-07-30
Date: Tue, 23 Jul 2013 15:51:28 +0200 [thread overview]
Message-ID: <87a9ldpeov.fsf@elfo.elfo> (raw)
In-Reply-To: <877gghqvnd.fsf@elfo.elfo> (Juan Quintela's message of "Tue, 23 Jul 2013 14:59:50 +0200")
Juan Quintela <quintela@redhat.com> wrote:
> Juan Quintela <quintela@redhat.com> 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.
>
> I got the wrong day.
>
> Correct date was today (2013-07-22).
>
> Sorry for the confusion.
>
>
> Later, Juan.
2013-07-23!!
for i in ´seq 1 1000000´; do
printf "always use -m option with cal";
done
Once done this, I am going back to school to learn data arithmetic.
Sorry again :-(
prev parent reply other threads:[~2013-07-23 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 6:33 [Qemu-devel] KVM call agenda for 2013-07-30 Juan Quintela
2013-07-23 7:55 ` Christian Borntraeger
2013-07-23 12:55 ` Peter Maydell
2013-07-23 12:59 ` Juan Quintela
2013-07-23 13:51 ` Juan Quintela [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=87a9ldpeov.fsf@elfo.elfo \
--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 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).