From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Martin Fouts" <Martin.Fouts@palmsource.com>
Cc: <jesper.juhl@gmail.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Why don't we separate menuconfig from the kernel?
Date: 18 Sep 2005 12:36:03 +0200 [thread overview]
Message-ID: <m3zmqaek8c.fsf@defiant.localdomain> (raw)
In-Reply-To: <DE88BDF02F4319469812588C7950A97E93121E@ussunex1.palmsource.com>
"Martin Fouts" <Martin.Fouts@palmsource.com> writes:
> I don't have a patch yet, but I've just spent a bit of time looking at
> how kbuild works, and I believe there is a fairly straightforward way to
> keep kbuild in the kernel tree but make it easy to split it out so that
> someone could use it as a separate tool.
That is obvious and people already are doing that, what I'm thinking of is
moving menuconfig or *config out of the kernel so there is one well-defined
external package.
--
Krzysztof Halasa
next prev parent reply other threads:[~2005-09-18 10:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 1:53 Why don't we separate menuconfig from the kernel? Martin Fouts
2005-09-18 7:30 ` Sam Ravnborg
2005-09-18 10:36 ` Krzysztof Halasa [this message]
2005-09-18 10:55 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2005-09-18 7:50 Martin Fouts
2005-09-17 17:16 Krzysztof Halasa
2005-09-17 17:33 ` Michal Piotrowski
2005-09-17 19:18 ` Krzysztof Halasa
2005-09-18 0:46 ` Jesper Juhl
2005-09-18 0:56 ` Randy.Dunlap
2005-09-18 0:58 ` Jesper Juhl
2005-09-18 1:05 ` Krzysztof Halasa
2005-09-18 1:16 ` Jesper Juhl
2005-09-18 10:33 ` Krzysztof Halasa
2005-09-18 20:40 ` Daniel Barkalow
2005-09-19 7:15 ` Matthias Andree
2005-09-19 16:28 ` Krzysztof Halasa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zmqaek8c.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=Martin.Fouts@palmsource.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.