To: L A Walsh <lkml@tlinx.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reviving the concept of a stable series
References: <200501031424.j03EOV2t029019@laptop11.inf.utfsm.cl>
	<41E07711.3040008@tlinx.org>
From: Adam Sampson <azz@us-lot.org>
Organization: Things I did not know at first I learned by doing twice.
Date: Mon, 10 Jan 2005 13:44:08 +0000
In-Reply-To: <41E07711.3040008@tlinx.org> (L. A. Walsh's message of "Sat, 08
 Jan 2005 16:13:05 -0800")
Message-ID: <y2ais65z9ef.fsf@cartman.at.fivegeeks.net>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through
 Obscurity, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 978
Lines: 23

L A Walsh <lkml@tlinx.org> writes:

> If you have a better way of creating a stable series of kernels
> coming off kernel.org, I'm not attached to any specific method of
> "how".

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?

-- 
Adam Sampson <azz@us-lot.org>                        <http://offog.org/>
-
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/