Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751091AbVIRKzz (ORCPT ); Sun, 18 Sep 2005 06:55:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751115AbVIRKzz (ORCPT ); Sun, 18 Sep 2005 06:55:55 -0400 Received: from mta09-winn.ispmail.ntl.com ([81.103.221.49]:64174 "EHLO mta09-winn.ispmail.ntl.com") by vger.kernel.org with ESMTP id S1751091AbVIRKzy (ORCPT ); Sun, 18 Sep 2005 06:55:54 -0400 Subject: Re: Why don't we separate menuconfig from the kernel? From: Ian Campbell To: Krzysztof Halasa Cc: Martin Fouts , jesper.juhl@gmail.com, linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Date: Sun, 18 Sep 2005 11:55:49 +0100 Message-Id: <1127040949.3144.3.camel@insmouth> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 729 Lines: 21 On Sun, 2005-09-18 at 12:36 +0200, Krzysztof Halasa wrote: > What I'm thinking of is moving menuconfig or *config out of the > kernel so there is one well-defined external package. If you really think it is worthwhile you could start maintaining a package containing a copy of *config from the most recent kernel for all these other projects to use, that would reduce the number of copies to just 2, it would be a good start... Ian. -- Ian Campbell Void where prohibited by law. - 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/