Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 10 Apr 2002 00:57:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 10 Apr 2002 00:57:40 -0400 Received: from 60.54.252.64.snet.net ([64.252.54.60]:14180 "EHLO hotmale.boyland.org") by vger.kernel.org with ESMTP id ; Wed, 10 Apr 2002 00:57:39 -0400 Message-ID: <3CB3C6F5.4020706@blue-labs.org> Date: Wed, 10 Apr 2002 01:00:37 -0400 From: David Ford User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+) Gecko/20020402 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adam McKenna CC: linux-kernel@vger.kernel.org Subject: Re: The latest -ac patch to the stable Linux kernels In-Reply-To: <20020409230116.GB22300@flounder.net> <3CB37B1F.2050405@blue-labs.org> <20020409233710.GD22300@flounder.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Well, shortly put, the -ac tree is much more -pre than the -pre patches are. Using -ac patches is jumping ahead of the -pre patches normally. -d Adam McKenna wrote: >On Tue, Apr 09, 2002 at 07:37:03PM -0400, David Ford wrote: > >>Not at all. >> >>Alan's most recent patch is in line with the 2.4.19 series of patches, >>these are pre patches to the upcoming 2.4.19. >> > >Right, but (as far as I know) 2.4.19-pre6 is not considered the "stable linux >kernel", is it? So how could 2.4.19-pre5-ac3 be the latest -ac patch to the >stable linux kernel? It's more like "the latest -ac patch to the latest >prepatch for the stable linux kernel". > >What I'm really complaining about is that for people who don't like to use >-pre kernels (like me), finger@finger.kernel.org is useless for finding out >what the latest -ac patch is to a non-pre kernel. > - 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/