Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S281427AbRKMBdW>; Mon, 12 Nov 2001 20:33:22 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S281425AbRKMBdM>; Mon, 12 Nov 2001 20:33:12 -0500
Received: from cambot.suite224.net ([209.176.64.2]:23053 "EHLO suite224.net")
	by vger.kernel.org with ESMTP id <S281427AbRKMBdF>;
	Mon, 12 Nov 2001 20:33:05 -0500
Message-ID: <001501c16be3$a5b16860$1df583d0@pcs586>
From: "Matthew D. Pitts" <mpitts@suite224.net>
To: =?ISO-8859-1?Q? "Fran=E7ois?= Cami" <stilgar2k@wanadoo.fr>,
        "Sean Elble" <S_Elble@yahoo.com>
Cc: <joeja@mindspring.com>, "John Alvord" <jalvo@mbay.net>,
        <linux-kernel@vger.kernel.org>
In-Reply-To: <Springmail.105.1005596822.0.40719200@www.springmail.com> <00c701c16bd2$e4b11800$0a00a8c0@intranet.mp3s.com> <3BF06B44.1040709@wanadoo.fr> <015101c16bdc$e633dbe0$0a00a8c0@intranet.mp3s.com> <3BF07147.5050503@wanadoo.fr>
Subject: Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)
Date: Mon, 12 Nov 2001 20:35:42 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-15"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Umm... Linus, when are you going to open the 2.5.x development cycle? That
is how we used to catch this kind of thing.

Matthew D. Pitts
Pitts Computer Services
mpitts@suite224.net
----- Original Message -----
From: "Fran?ois Cami" <stilgar2k@wanadoo.fr>
To: "Sean Elble" <S_Elble@yahoo.com>
Cc: <joeja@mindspring.com>; "John Alvord" <jalvo@mbay.net>;
<linux-kernel@vger.kernel.org>
Sent: Monday, November 12, 2001 8:03 PM
Subject: Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop
back broken in 2.2.14)


>
> I am wondering too... Anyone got ideas on this ?
>
> I would like to avoid some specific problems... especially
> bugs that show up when compiling a certain module / feature
> of the kernel, like the loopback in 2.4.14.
>
> Those should be very easy to get rid of
> [it only takes some kernel testers to debug that early, if only
> there actually were a feature freeze that last for one day...].
>
> Fran?ois


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