Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 20 Mar 2003 18:39:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 20 Mar 2003 18:39:13 -0500 Received: from pc2-cwma1-4-cust86.swan.cable.ntl.com ([213.105.254.86]:23698 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Thu, 20 Mar 2003 18:39:12 -0500 Subject: Re: Release of 2.4.21 From: Alan Cox To: Adrian Knoth Cc: Linux Kernel Mailing List In-Reply-To: <20030320195657.GA3270@drcomp.erfurt.thur.de> References: <20030320195657.GA3270@drcomp.erfurt.thur.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1048208493.4031.3.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 21 Mar 2003 01:01:34 +0000 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 603 Lines: 14 On Thu, 2003-03-20 at 19:56, Adrian Knoth wrote: > (and glibc as well) to do the same. You cannot call 2.4.20 a stable kernel > with such a bug, so as a leader of the 2.4.x-series you cannot call the > whole branch "stable". > > World needs to update, best way to enforce is by a new release. The vendors have released updated kernels. Whats the problem ? - 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/