From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: 3.0.3 freeze
Date: Mon, 28 Aug 2006 16:21:14 +0100 [thread overview]
Message-ID: <20060828152114.GD862@redhat.com> (raw)
In-Reply-To: <C118C560.EAA%Keir.Fraser@cl.cam.ac.uk>
On Mon, Aug 28, 2006 at 04:08:00PM +0100, Keir Fraser wrote:
> On 28/8/06 3:58 pm, "Daniel P. Berrange" <berrange@redhat.com> 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.
Yes, the re-factoring does look like a good idea from a long term maintenance
POV - it just caught us a little by surprise ! Thanks for clarifying the
current branch situation.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2006-08-28 15:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 16:03 3.0.3 freeze Ian Pratt
2006-08-22 16:34 ` Sean Dague
2006-08-22 21:00 ` Ryan Harper
2006-08-22 21:12 ` Subrahmanian, Raj
2006-08-25 0:53 ` Tuan Van
2006-08-28 14:58 ` Daniel P. Berrange
2006-08-28 15:08 ` Keir Fraser
2006-08-28 15:21 ` Daniel P. Berrange [this message]
2006-08-28 15:49 ` Daniel Veillard
2006-08-28 16:32 ` Keir Fraser
2006-08-28 16:47 ` Rik van Riel
2006-08-28 16:48 ` Keir Fraser
2006-08-28 17:12 ` Rik van Riel
2006-08-28 17:19 ` Keir Fraser
2006-08-28 17:56 ` Daniel Veillard
2006-09-12 11:06 ` Anthony Wright
2006-09-12 11:40 ` Ian Pratt
2006-09-12 12:55 ` Anthony Wright
2006-09-12 13:45 ` Matt Ayres
2006-09-12 22:00 ` John Lenz
2006-09-13 9:33 ` Nicholas Lee
2006-09-19 11:21 ` Anthony Wright
2006-09-19 12:56 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2006-08-28 15:22 Ian Pratt
2006-08-28 16:48 Ian Pratt
2006-08-28 17:03 ` Daniel P. Berrange
2006-08-28 20:16 ` Daniel Veillard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060828152114.GD862@redhat.com \
--to=berrange@redhat.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.