Subject: Re: Reviving the concept of a stable series
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adam Sampson <azz@us-lot.org>
Cc: L A Walsh <lkml@tlinx.org>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
In-Reply-To: <y2ais65z9ef.fsf@cartman.at.fivegeeks.net>
References: <200501031424.j03EOV2t029019@laptop11.inf.utfsm.cl>
	 <41E07711.3040008@tlinx.org>  <y2ais65z9ef.fsf@cartman.at.fivegeeks.net>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1105383229.12028.104.camel@localhost.localdomain>
Mime-Version: 1.0
Date: Mon, 10 Jan 2005 19:24:02 +0000
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1078
Lines: 22

On Llu, 2005-01-10 at 13:44, Adam Sampson wrote:
> L A Walsh <lkml@tlinx.org> writes:
> One option would be a "Linux Legacy" project, similar to the Fedora
> Legacy project that backports updates to old Red Hat/Fedora Core
> releases: a central service that'd collect bug fixes for released
> kernels that distributors could then base their kernels on. That way,
> we'd get the stability advantages of vendor kernels without needing to
> repeat the effort for each distribution.
> 
> Maybe some of the distribution vendors might be interested in setting
> up something like this?

It would be essentially unmanageable unless you picked only one specific
kernel and configuration set to support. Needless to say you won't find
vendors even ship the same kernel. Nor for that matter would a few
backports magically give you stability.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/