Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 6 Jun 2002 17:36:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 6 Jun 2002 17:36:38 -0400 Received: from louise.pinerecords.com ([212.71.160.16]:12552 "EHLO louise.pinerecords.com") by vger.kernel.org with ESMTP id ; Thu, 6 Jun 2002 17:36:37 -0400 Date: Thu, 6 Jun 2002 23:36:29 +0200 From: Tomas Szepe To: Jesse Pollard Cc: linux-kernel@vger.kernel.org Subject: Re: If you want kbuild 2.5, tell Linus Message-ID: <20020606213628.GK17859@louise.pinerecords.com> In-Reply-To: <200206062101.QAA15457@tomcat.admin.navo.hpc.mil> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-OS: GNU/Linux 2.4.19-pre10/sparc SMP X-Uptime: 2 days, 7:11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > How about the following approach, which MAY not be practical: Please note that there have already been innumerable proposals of how to merge kbuild 2.5, and all of them have been silently rejected. What I keep pondering over is, what is it that Linus finds troublesome about merging the whole of kbuild 2.5? More -- why has he decided to keep this to himself? Something tells me the answer to these questions might be the key to solving the whole kb25 merge problem. Hmmmm, it's rather odd to have to write about someone in 3rd person when you know they'll read the text; They'll even give it a bit of thought and will likely have things to say. They won't let you know, though. You've noticed Linus was a he in the "if you want kbuild 2.5, tell Linus" mail, haven't you? If I was a psychologist, I might have something interesting to say based on that information. :) Oh well. And as for your idea, I'd say it really is impractical. kbuild 2.5 can live in perfect peace with the old build system as it is. T. - 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/