From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 14 Jun 2001 05:07:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 14 Jun 2001 05:07:16 -0400 Received: from matrix.fr.professo.net ([213.11.43.1]:30222 "EHLO fr.professo.net") by vger.kernel.org with ESMTP id ; Thu, 14 Jun 2001 05:06:58 -0400 Message-ID: <003d01c0f4b1$4bf65f00$c200a8c0@professo.lan> From: "Ghozlane Toumi" To: "Alan Cox" , "Rainer Mager" Cc: In-Reply-To: Subject: Re: obsolete code must die Date: Thu, 14 Jun 2001 11:06:18 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org ----- Original Message ----- From: "Alan Cox" Subject: Re: obsolete code must die > > Would it make sense to create some sort of 'make config' script that > > determines what you want in your kernel and then downloads only those > > components? After all, with the constant release of new hardware, isn't a > > 50MB kernel release not too far away? 100MB? > > This should be a FAQ entry. actually, it *is* a FAQ entry ... http://www.tux.org/lkml/#s7-7 ghoz