Glauber Costa wrote:
As we're getting close to kvm-xxx anyway, maybe we could forget this number scheme, and adopt something that tracks linux. This way, you know exactly what kernel a released is based on. Something in the lines of kvm-29.1 for updates to the .29 series, (of course _this_ scheme is bad, because it brings clashes)
It also ignores qemu, which is larger contributor to user visible features...
Maybe stable releases should have separate packages for kvm and qemu: kvm-modules-2.6.29.1 and qemu-kvm-0.9.1.17. Users would pick the latest of each, and would only need to upgrade a component that's changed.
-- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
