On 01/10/2010 04:49 PM, Gleb Natapov wrote:
If the feature is already in both, then morph qemu-kvm.git into what
is already in qemu.git. Hopefully anything missing in qemu.git will
be discovered while making the changes.
What about bugs that are present only in qemu.git? Like this:
http://patchwork.ozlabs.org/patch/42298/. Should it go through
qemu-kvm.git/uq/master?
Yes. So there is a central place for kvm patches, and so they see autotest.
What about this one: http://patchwork.ozlabs.org/patch/42447/ should it
be postponed untill qemu.git and qemu-kvm.git converge on using the same
cpuid infrastructure, or add similar functionality to qemu-kvm to,
or add new cpu flags to qemu-kvm only and when cpuid code converge
qemu.git will have it too?
Best to make qemu-kvm.git and qemu.git converge first. Duplicating the
patch extends the problem. Of course if something is urgent we can
bypass the process.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
