From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: xen-devel@lists.xensource.com
Subject: Xen v.s Stable Kernel
Date: Thu, 25 Jan 2007 01:22:53 +0200 [thread overview]
Message-ID: <200701250122.57722.caglar@pardus.org.tr> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 939 bytes --]
Hi All;
I can't find any related discussion on list archives so i just want to learn
could anybody tell me is there any specific reason not to upgrade
xen-3.0.4-testing tree to for example 2.6.16.38 which fixes dozens of
security related problems after .33, i know as a distro packager its my
responsibility to sync/modify whatever is needed but as an end-user
perspective i just want to download the newly released stable tarball and use
my xen powered kernel. And i realize mainline inclusion solves all that
issues but is it possible to maintain testing trees against its most recent
stable version to solve these problems until xen merged into mainline and
releasing minor version against them or am i have to learn live with that :)?
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2007-01-24 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 23:22 S.Çağlar Onur [this message]
2007-01-24 23:35 ` Xen v.s Stable Kernel Ian Pratt
2007-01-24 23:45 ` S.Çağlar Onur
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=200701250122.57722.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--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.