From: Juan Quintela <quintela@redhat.com>
To: Developers qemu-devel <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: KVM call minutes December 13th
Date: Tue, 13 Dec 2011 16:54:36 +0100 [thread overview]
Message-ID: <87ehw831s3.fsf@trasno.mitica> (raw)
Hi
- monitor command async framework
* how to merge async command?
- merge all QAPI (will take until the end of the release)
- let things as they are
- use a new corroutine for each async command, so the error can be
maintained on each corrutine.
* currently only one async command
- QOM merge strategy
* series of 800 commits or so
* several of them created with scripts that touches almost all of file
(no way/reason to review each patch, better to publish the scripts)
- qemu.org change to a new server (thank Anthony and Stephan)
* in the proccess of switching
- stable tree: will be create in the new tree
- ibm starting a new project on sandboxing qemu.
* anthony suggest that they start showing what they are doing the
sooner, the better
* once there, start with things that make sense for themselves, i.e. don't
wait until everything "works" to try to merge anything
- Call is cancelled until next year (Tuesday 3rd)
So, happy Christmas/vacation to everybody.
Later, Juan.
reply other threads:[~2011-12-13 15:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87ehw831s3.fsf@trasno.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox