From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269700AbUJGHwk (ORCPT ); Thu, 7 Oct 2004 03:52:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269745AbUJGHwk (ORCPT ); Thu, 7 Oct 2004 03:52:40 -0400 Received: from stutter.bur.st ([202.61.227.61]:46117 "EHLO stutter.bur.st") by vger.kernel.org with ESMTP id S269700AbUJGHwh (ORCPT ); Thu, 7 Oct 2004 03:52:37 -0400 Date: Thu, 7 Oct 2004 15:52:35 +0800 From: Trent Lloyd To: Chuck Ebbert <76306.1226@compuserve.com>, linux-kernel@vger.kernel.org Subject: Re: Why no linux-2.6.8.2? (was Re: new dev model) Message-ID: <20041007075235.GB13436@sweep.bur.st> References: <200410070308_MC3-1-8BB4-FF92@compuserve.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200410070308_MC3-1-8BB4-FF92@compuserve.com> X-Random-Number: -inf User-Agent: Mutt/1.5.6+20040722i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, > > 2.6.8.1 was released because there was a 1-line error in 2.6.8 that > > completely stopped NFS from working. > Yes, I know that. > > > The patches mentioned below will probably go into 2.6.9 or something, if > > they have been approved for it etc. > > > > A host of new bugs will probably be added too, leaving the average user with > no stable 'offical' kernel to use -- ever. Well that's a different argument over whether to branch into 2.7 yet or not But please, can we not go there... Cheers, Trent Bur.st -- Trent Lloyd Bur.st Networking Inc.