From: Jean Delvare <khali@linux-fr.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Adrian Bunk <bunk@stusta.de>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.30-pre1
Date: Sat, 23 Sep 2006 23:20:54 +0200 [thread overview]
Message-ID: <20060923232054.4964f729.khali@linux-fr.org> (raw)
In-Reply-To: <1159045077.1097.182.camel@mindpipe>
Hi Lee,
> On Sat, 2006-09-23 at 22:49 +0200, Jean Delvare wrote:
> > I will not use 2.6.16.y with its current rules, for sure, and I doubt
> > any distribution will. Wasn't the whole point of 2.6.16.y to serve as
> > a common base between several distributions?
>
> I would not expect distros to be interested in a 2.6 tree that does not
> add support for new devices. Isn't new hardware support one of the main
> areas where distros routinely get ahead of mainline?
It really depends on the distribution, and even more of the specific
product. I know for a fact that Suse has no interest in supporting
additional hardware in the saa7134 driver for SLES10, for example. I
suspect that distributions only backport hardware support when a
customer asks for it, and they have some in-house knowledge to do it
safely.
My original understanding was that 2.6.16.y was meant to be a common
tree between different distributions and products, containing only the
unquestionable fixes - i.e. security, data corruption and other oopses,
in the -stable spirit - and then different distributions would add their
own patches on top of it as they see fit.
--
Jean Delvare
next prev parent reply other threads:[~2006-09-23 21:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 22:23 Linux 2.6.16.30-pre1 Adrian Bunk
2006-09-22 22:38 ` Greg KH
2006-09-22 22:47 ` Adrian Bunk
2006-09-22 23:09 ` Greg KH
2006-09-23 4:56 ` Willy Tarreau
2006-09-23 23:21 ` Adrian Bunk
2006-09-23 23:53 ` Willy Tarreau
2006-09-24 7:46 ` Sergey Vlasov
2006-09-24 18:16 ` Adrian Bunk
2006-09-24 19:46 ` Stefan Richter
2006-09-24 19:44 ` Willy Tarreau
2006-09-24 20:02 ` Willy Tarreau
2006-09-25 1:01 ` Adrian Bunk
2006-09-24 10:17 ` Pavel Machek
2006-09-25 1:23 ` Adrian Bunk
2006-09-25 8:15 ` Pavel Machek
2006-09-27 5:14 ` Greg KH
2006-09-23 20:49 ` Jean Delvare
2006-09-23 20:57 ` Lee Revell
2006-09-23 21:20 ` Jean Delvare [this message]
2006-09-23 22:47 ` Adrian Bunk
2006-09-23 22:33 ` Adrian Bunk
2006-09-23 22:47 ` Lee Revell
2006-09-23 22:58 ` Adrian Bunk
2006-09-23 22:12 ` Adrian Bunk
2006-09-24 10:12 ` Pavel Machek
2006-09-25 1:20 ` Adrian Bunk
2006-09-24 20:25 ` Grant Coady
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=20060923232054.4964f729.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox