From: Keir Fraser <keir@xensource.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: "Zulauf, John" <john.zulauf@intel.com>, xen-devel@lists.xensource.com
Subject: Re: Timeline for migrating to newer Linux kernels?
Date: Tue, 02 Jan 2007 10:07:11 +0000 [thread overview]
Message-ID: <C1BFDF4F.6F81%keir@xensource.com> (raw)
In-Reply-To: <20070102094918.GC3351@redhat.com>
On 2/1/07 09:49, "Daniel P. Berrange" <berrange@redhat.com> wrote:
>> As for the Linux sparse tree in xen-unstable, it will be upgraded and moved
>> to a separate repository before 3.0.5. With the guest kernel interfaces
>> having been stable for some time, it makes lots of sense to separate
>> hypervisor development and its release cycle from that of guest kernels.
>
> When you say 'guest' kernel interfaces are you simply refering to DomU,
> or also Dom0 ? Having a separate repository / tree which only did the
> DomU kernel would be little use for Fedora, because we track the latest
> upstream kernels for both Dom0 and DomU. So I'd hope the separate kernel
> tree would cover Dom0 & DomU - is this what's planned ?
We will have a separate repository that has the same feature set as the
current integrated sparse tree -- i.e., it will support both dom0 and domU.
-- Keir
next prev parent reply other threads:[~2007-01-02 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 19:31 Timeline for migrating to newer Linux kernels? Zulauf, John
2007-01-01 0:21 ` Rik van Riel
2007-01-01 16:44 ` Keir Fraser
2007-01-02 9:49 ` Daniel P. Berrange
2007-01-02 10:07 ` Keir Fraser [this message]
2007-01-10 2:54 ` Jimi Xenidis
2007-01-02 1:20 ` Jeremy Fitzhardinge
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=C1BFDF4F.6F81%keir@xensource.com \
--to=keir@xensource.com \
--cc=berrange@redhat.com \
--cc=john.zulauf@intel.com \
--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.