On Tue, 2012-03-27 at 12:09 +0200, Avi Kivity wrote: > That's fine if there are no interdependencies. It looks like 74df956 > will be a problem though. > > The other two options are: > > - I'll add my signoff to the commits that lack it. This unbreaks the > committer lacks signoff. > - I remove Alex's commits, Alex sends me a pull request based on that > tree, I pull it in. Alex being away for three weeks is a minor flaw in > this plan. > - As above, but with you sending me that tree as temporary kvm-ppc > maintainer. > > Options 2/3 are harder as there are a few interdependencies. > > Linus, if the first option is acceptable, a tree is available at the > same place: > > git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/3.4 > > otherwise, please provide guidance. Linus, what's your feeling here ? I'd really like to have the bulk of the powerpc updates this time around, they already missed the previous merge window due to maintainers taking too long to deal with their inbox :-) KVM ppc is a big WIP with little if any users at this point so the risk of breaking things is near to non-existent, it all boils down to making our own life easier by having stuff not drifting out of tree (and making it possible for distros to pick it up when they decide to do so). Cheers, Ben. -- 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
