From: Tim Post <echo@echoreply.us>
To: Jan Beulich <JBeulich@novell.com>
Cc: Andrew Lyon <andrew.lyon@gmail.com>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: 2.6.30 dom0 Xen patches
Date: Mon, 06 Jul 2009 21:58:10 +0800 [thread overview]
Message-ID: <1246888690.5517.276.camel@localhost.localdomain> (raw)
In-Reply-To: <4A5212670200007800008F6F@vpn.id2.novell.com>
Hi,
On Mon, 2009-07-06 at 14:04 +0100, Jan Beulich wrote:
> >>> Pasi Kärkkäinen<pasik@iki.fi> 06.07.09 13:02 >>>
> >I assume Novell did a lot of testing/patching/bugfixing for SLES11 2.6.27
> >Xen kernel. Do these OpenSUSE Xen patches contain the fixes from SLES11?
>
> Yes, OpenSuSE and SLE11 have been sharing the kernel approximately since
> the release of the first kernel maintenance update for SLE11.
>
> Jan
Is there a consensus now on where the 2.6.30-xen tree is going to live?
I saw a mention of space on xenbits, but did not see a consensus. Did I
miss one in the thread?
No rush or anything, I'm just catching up to the thread and feel as if I
missed a reply or two.
Cheers,
--Tim
next prev parent reply other threads:[~2009-07-06 13:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 17:15 2.6.30 dom0 Xen patches Andrew Lyon
2009-07-01 18:31 ` Andrew Lyon
2009-07-11 11:09 ` dbaxps
2009-07-01 18:47 ` 2.6.30.1-rc1 dom0 tarball Daniel Schroeder
2009-07-02 6:53 ` 2.6.30 dom0 Xen patches Jan Beulich
2009-07-06 11:02 ` Pasi Kärkkäinen
2009-07-06 13:04 ` Jan Beulich
2009-07-06 13:58 ` Tim Post [this message]
[not found] ` <f4527be0907030448i305f2f24y318110fc9d02dbdb@mail.gmail.com>
[not found] ` <4A4E1FDB0200007800008C9B@vpn.id2.novell.com>
2009-07-17 18:11 ` Andrew Lyon
2009-07-02 9:22 ` 2.6.30.1-rc2 dom0 tarball Daniel Schroeder
2009-07-03 6:42 ` updated dom0 tarballs Daniel Schroeder
2009-07-16 22:56 ` 2.6.30 dom0 Xen patches Kris Shannon
-- strict thread matches above, loose matches on Subject: below --
2009-07-02 15:51 Boris Derzhavets
2009-07-07 17:12 Boris Derzhavets
2009-07-10 8:00 ` Jan Beulich
2009-07-08 16:45 Boris Derzhavets
2009-07-10 8:09 Boris Derzhavets
2009-07-10 8:22 ` Jan Beulich
2009-07-10 8:26 Boris Derzhavets
2009-07-10 8:55 ` Jan Beulich
2009-07-10 9:31 Boris Derzhavets
2009-07-10 12:40 Boris Derzhavets
2009-07-10 12:52 ` Jan Beulich
2009-07-10 15:11 Boris Derzhavets
2009-07-17 7:11 Boris Derzhavets
2009-07-17 10:06 ` Pasi Kärkkäinen
2009-07-17 10:14 Boris Derzhavets
2009-07-17 10:19 Boris Derzhavets
2009-07-17 10:38 ` Pasi Kärkkäinen
2009-07-17 12:57 Boris Derzhavets
2009-07-17 13:28 ` Jan Beulich
2009-07-17 21:14 Boris Derzhavets
2009-07-17 23:07 ` Jun Koi
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=1246888690.5517.276.camel@localhost.localdomain \
--to=echo@echoreply.us \
--cc=JBeulich@novell.com \
--cc=andrew.lyon@gmail.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.