And a couple follow-up questions...
Will xen-unstable move forward to (at least) 2.6.18 now?
Will the tree structure change from the current sparse model to
a fully-populated kernel? IMHO it wouldn't be too hard to use
something similar to
http://xenbits.xensource.com/ext/linux-2.6.tip-xen.hg plus a top-level
xen directory containing the hypervisor. Alternatively, since Xen
isn't just Linux, maybe the hypervisor and kernels should be in
separate repositories?
Aron
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel