Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268736AbTGVUPW (ORCPT ); Tue, 22 Jul 2003 16:15:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268822AbTGVUPW (ORCPT ); Tue, 22 Jul 2003 16:15:22 -0400 Received: from pub234.cambridge.redhat.com ([213.86.99.234]:14604 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S268736AbTGVUPV (ORCPT ); Tue, 22 Jul 2003 16:15:21 -0400 Date: Tue, 22 Jul 2003 21:30:17 +0100 (BST) From: James Simmons To: Samuel Flory cc: Sam Ravnborg , Christoph Hellwig , Roman Zippel , michaelm , Linux Kernel Mailing List , Vojtech Pavlik Subject: Re: Make menuconfig broken In-Reply-To: <3F1D91F0.2020900@rackable.com> 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: 838 Lines: 22 > Well there are 2 issues here: > > 1) How to handle "make oldconfig" on 2.4 config files. Which may not be > fixable in a manner that doesn't involve really ugly code. > > 2) That make menuconfig|xconfig on a clean 2.6 tree results in a kernel > that doesn't have console support. This will be something that will > come up over and over again in the future, and does not require ugly > hacks to fix. Instead of hacking up a oldconfig why not have the system detect old config files and refuse to build it and tell the user to start from scratch. I think this is acceptable. - 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/