Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S282719AbRK0Bh5>; Mon, 26 Nov 2001 20:37:57 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S282720AbRK0Bhr>; Mon, 26 Nov 2001 20:37:47 -0500
Received: from 216-21-153-1.ip.van.radiant.net ([216.21.153.1]:1544 "HELO
	innerfire.net") by vger.kernel.org with SMTP id <S282718AbRK0Bhb>;
	Mon, 26 Nov 2001 20:37:31 -0500
Date: Mon, 26 Nov 2001 18:40:04 -0800 (PST)
From: Gerhard Mack <gmack@innerfire.net>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
cc: John Jasen <jjasen1@umbc.edu>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Releases 
In-Reply-To: <200111262036.fAQKaSwF009666@pincoya.inf.utfsm.cl>
Message-ID: <Pine.LNX.4.10.10111261838220.11513-100000@innerfire.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, 26 Nov 2001, Horst von Brand wrote:

> AFAIU, if Linus (or whoever) puts out a -preX, it is because according to
> _their_ testing (limited, whatever) it is "almost done, please check". If
> they put out a non-pre, it is because they don't see any more issues with
> it. The _only_ way they can ever know something breaks is that _somebody_
> (yes, I _do_ mean you) checks it out and complains beforehand.

This is not always correct.. I've seen countless -pre kernels released as
synch points with a warning in the changelog.

It is a matter of not messing with pre series kernels unless you are
willing to read the changelogs.
 
	Gerhard

--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.

-
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/