From: "Andreas Färber" <afaerber@suse.de>
To: quintela@redhat.com, KVM devel mailing list <kvm@vger.kernel.org>,
qemu list <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Anthony Liguori <aliguori@amazon.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Bruce Rogers <brogers@suse.com>
Subject: Re: [Qemu-devel] KVM call agenda for 2014-04-01
Date: Mon, 31 Mar 2014 12:51:31 +0200 [thread overview]
Message-ID: <533948B3.2070009@suse.de> (raw)
In-Reply-To: <87mwg6ejn8.fsf@elfo.mitica>
Hi,
Am 31.03.2014 12:40, schrieb Juan Quintela:
>
> Please, send any topic that you are interested in covering.
I would like to discuss the state of the QEMU release process, please:
* -rc1 has not been tagged.
* Who besides Anthony could upload a tarball if we tag and create it?
* make-release fix for SeaBIOS on the list. Ping, and are more affected?
Thanks,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-03-31 10:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 10:40 [Qemu-devel] KVM call agenfda for 2014-04-01 Juan Quintela
2014-03-31 10:51 ` Andreas Färber [this message]
2014-03-31 12:07 ` [Qemu-devel] KVM call agenda " Stefan Hajnoczi
2014-03-31 13:21 ` Christian Borntraeger
2014-03-31 13:25 ` Peter Maydell
2014-03-31 14:01 ` Anthony Liguori
2014-03-31 14:28 ` Paolo Bonzini
2014-03-31 14:32 ` Peter Maydell
2014-03-31 14:46 ` Andreas Färber
2014-03-31 15:42 ` Anthony Liguori
2014-03-31 16:58 ` Markus Armbruster
2014-03-31 19:57 ` Michael Roth
2014-04-01 8:16 ` Peter Maydell
2014-04-01 12:39 ` [Qemu-devel] KVM call agenfda " Juan Quintela
2014-04-10 15:49 ` Alexander Graf
2014-04-10 15:52 ` Peter Maydell
2014-04-10 15:57 ` Alexander Graf
2014-04-10 16:16 ` Stuart Yoder
2014-04-11 7:46 ` Markus Armbruster
2014-04-11 9:17 ` Alexander Graf
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=533948B3.2070009@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=anthony@codemonkey.ws \
--cc=brogers@suse.com \
--cc=kvm@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@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).