Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 13 Jan 2003 09:58:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 13 Jan 2003 09:58:23 -0500 Received: from hermes.fachschaften.tu-muenchen.de ([129.187.202.12]:52721 "HELO hermes.fachschaften.tu-muenchen.de") by vger.kernel.org with SMTP id ; Mon, 13 Jan 2003 09:58:22 -0500 Date: Mon, 13 Jan 2003 16:07:08 +0100 From: Adrian Bunk To: "Richard B. Tilley \(Brad\)" Cc: "linux-kernel@vger.kernel.org" Subject: Re: Bugs and Releases Numbers Message-ID: <20030113150708.GI21826@fs.tum.de> References: <1042469616.28005.36.camel@oubop4.bursar.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1042469616.28005.36.camel@oubop4.bursar.vt.edu> User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 13, 2003 at 09:53:36AM -0500, Richard B. Tilley (Brad) wrote: > Hello, Hi Richard, > How are bug patches worked into the current stable release? For example, > the ext3 file corruption bug in 2.4.20, was that patch worked into the > kernel or will it be included in 2.4.21? I'm confused about the exact > details of this type of thing. If the patch was worked in to 2.4.20, how > can one tell as the release number doesn't/hasn't changed? >... the kernel that was released as 2.4.20 will never be changed. The ext3 problems are fixed in the 2.4.21-pre kernels and the fixed ext3 code will be in 2.4.21. > Thank you, > > Brad cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed - 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/