| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] 3.0.3 freeze
On 28/8/06 3:58 pm, "Daniel P. Berrange" <berrange@xxxxxxxxxx> wrote:
> Is this change going into 3.0.3, or is xen-unstable now reflecting the
> development for 3.0.4 ? We've got the means to support this new format
> for hypercalls in libvirt, while keeping compatability for old API
> (detectable at runtime), but if its not going to 3.0.3 we can postpone
> this dev work...
All bug fixing is going on in the unstable tree: there has been no fork. I'm
now done with major refactorings (domctl/sysctl on Friday; shadow2->shadow
today). I wanted those in before 3.0.3 because, although large, they are
unlikely to break anything, and it is a pain to move patches across branches
after a fork when only one branch has a major code reorg applied to it. I
hope you'll agree that the hypercall refactoring has resulted in a cleaner
interface than the old dom0_ops, and that it is a useful goal to allow the
dom0 kernel and tools interfaces to evolve separately from each other.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home