From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: KVM minutes May 8th
Date: Tue, 08 May 2012 16:28:22 +0200 [thread overview]
Message-ID: <87obpy927t.fsf@elfo.elfo> (raw)
Hi
- Status of the 1.1 release
It looks like everything is to the plan, and only bugfixes should be allowed now.
- QEMU documentation
* Improve properties. Now there is no help when you use -device.
* Amit did something about it? Resurect that work?
* People don't write documentation.
* How to organize iit?
Some volunteer to look what we have and what we need?
* Volunteer documentation maintainer?
- Remove block migration in 1.1
It don't work so well, it complicates migration code, and we are building a replacement that works.
- Coreboot
Peter Stuge didn't make to the call. We need details about what are coreboot needs/want.
- Poll about time/day.
We haven't had a call for almost two weeks for one reason or another.
Is there a problem with the time/day? should we change them? Notice
that changes are not _trivial_ (sooner than current call is too early
for US West coast, and much later is too late for Israel). So we can
move it 1-2h late, and move to another day.
During the call, people "kind of" agreed that this time is a good as
anyother, but if you think that it is better to move it, just let us
know.
Thanks, Juan.
WARNING: multiple messages have this Message-ID (diff)
From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM minutes May 8th
Date: Tue, 08 May 2012 16:28:22 +0200 [thread overview]
Message-ID: <87obpy927t.fsf@elfo.elfo> (raw)
Hi
- Status of the 1.1 release
It looks like everything is to the plan, and only bugfixes should be allowed now.
- QEMU documentation
* Improve properties. Now there is no help when you use -device.
* Amit did something about it? Resurect that work?
* People don't write documentation.
* How to organize iit?
Some volunteer to look what we have and what we need?
* Volunteer documentation maintainer?
- Remove block migration in 1.1
It don't work so well, it complicates migration code, and we are building a replacement that works.
- Coreboot
Peter Stuge didn't make to the call. We need details about what are coreboot needs/want.
- Poll about time/day.
We haven't had a call for almost two weeks for one reason or another.
Is there a problem with the time/day? should we change them? Notice
that changes are not _trivial_ (sooner than current call is too early
for US West coast, and much later is too late for Israel). So we can
move it 1-2h late, and move to another day.
During the call, people "kind of" agreed that this time is a good as
anyother, but if you think that it is better to move it, just let us
know.
Thanks, Juan.
next reply other threads:[~2012-05-08 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 14:28 Juan Quintela [this message]
2012-05-08 14:28 ` [Qemu-devel] KVM minutes May 8th Juan Quintela
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=87obpy927t.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.