From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: KVM call of May 17th
Date: Tue, 17 May 2011 17:01:58 +0200 [thread overview]
Message-ID: <m31uzxweu1.fsf@neno.mitica> (raw)
Minutes of today KVM call:
- import of headers
in marcelo hands through kvm tree
- libtool integration
* autoconf
* gnulib -> if we move to glib, we have something similar for free
* recursive Makefile
Paolo item: propose timeline & plan on wiki, and discuss from there
- SCSI integration
* In future, this would go though Kevin
* this time done through list
- we are in feature freeze. No big changes allowed. Fixes & other not
to big things allowed. Rest of things should wait to next release.
- QAPI statics
* current plan: merge subset of glib branch to enable virt-agent
code generator and error reporting
* Hoping patches for this week
* after that, we can merge GMP conversion without woneding about the
previous item.
* after that, qconfig if people are interested
- qdev documentation patches
decentralized vs centralized
Anthony wants centralized, everybody else (that spoke) wants it
decentralized
pros/cons:
whatever does it, decides
reply other threads:[~2011-05-17 15:02 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=m31uzxweu1.fsf@neno.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