Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 4 Oct 2002 02:19:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 4 Oct 2002 02:19:54 -0400 Received: from 62-190-218-97.pdu.pipex.net ([62.190.218.97]:772 "EHLO darkstar.example.net") by vger.kernel.org with ESMTP id ; Fri, 4 Oct 2002 02:19:54 -0400 From: jbradford@dial.pipex.com Message-Id: <200210040633.g946XwV4000177@darkstar.example.net> Subject: Re: [OT] 2.6 not 3.0 - (WAS Re: [PATCH-RFC] 4 of 4 - New problem To: greg@kroah.com (Greg KH) Date: Fri, 4 Oct 2002 07:33:58 +0100 (BST) Cc: linux-kernel@vger.kernel.org In-Reply-To: <20021003223028.GB2221@kroah.com> from "Greg KH" at Oct 03, 2002 03:30:28 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1056 Lines: 32 > > Hmmm, then for 3.0 I'd vote for fully working and proven stable: > > Hm, how do you "prove" any of these are stable :) Hmm, yeah, I see what you mean, but for me, proved stable is a couple of years of being in a major distribution, with people actually using it. Now that major distributions no longer ship development kernels, (Slackware used to - I have slackware CDs with 1.3.x trees on them, for example), this is a less valid point. > > * Bluetooth > > Been there since 2.4 ..and I'm sure the three people actually using it haven't found any bugs yet ;-) > > * USB (2) > > Present in 2.5 (and 2.4 now too) ..and yet there are still complaints that it doesn't work every day on the list. > > * IEEE 1394 > > Been there since 2.4. Still marked as experimental, though. Not stable yet. John. - 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/