Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 1 Jan 2003 09:49:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 1 Jan 2003 09:49:45 -0500 Received: from tomts10.bellnexxia.net ([209.226.175.54]:64655 "EHLO tomts10-srv.bellnexxia.net") by vger.kernel.org with ESMTP id ; Wed, 1 Jan 2003 09:49:44 -0500 Date: Wed, 1 Jan 2003 09:57:20 -0500 (EST) From: "Robert P. J. Day" X-X-Sender: rpjday@dell To: John Bradford cc: szepe@pinerecords.com, Subject: Re: a few more "make xconfig" inconsistencies In-Reply-To: <200301011445.h01EjK3Q000861@darkstar.example.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 654 Lines: 19 On Wed, 1 Jan 2003, John Bradford wrote: > For 2.5, each subcategory can be 'collapsed', so this problem doesn't > really occur. there's one point i want to verify. the design of this hierarchical structure of kernel options is not going to simply affect "make xconfig", is it? i'm assuming that the way this hierarchy is designed will affect *all* of the possible make ???config variations, right? rday - 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/