From: Keith Owens <kaos@ocs.com.au>
To: Christoph Hellwig <hch@caldera.de>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] mconfig 0.20 available
Date: Sat, 17 Nov 2001 21:56:51 +1100 [thread overview]
Message-ID: <16782.1005994611@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 16 Nov 2001 17:38:40 BST." <20011116173840.A15515@caldera.de>
On Fri, 16 Nov 2001 17:38:40 +0100,
Christoph Hellwig <hch@caldera.de> wrote:
>The mconfig release 0.20 is now available.
>
>Mconfig is a tool to configure the linux kernel, similar to
>make {menu,x,}config, but written in C and with a proper yacc
>parser.
Christoph, could you explain why this is being added now and how it
compares to CML1 and/or CML2?
kbuild 2.[45] is completely agnostic about how .config and autoconf.h
are built, the only requirement is that .config be internally
consistent before it goes into the main build phase. I don't care how
.config is built, but I do want to understand why another version of
CML is being developed.
next prev parent reply other threads:[~2001-11-17 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 16:38 [ANNOUNCE] mconfig 0.20 available Christoph Hellwig
2001-11-17 10:56 ` Keith Owens [this message]
2001-11-17 17:32 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2001-11-18 11:38 Samium Gromoff
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=16782.1005994611@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=hch@caldera.de \
--cc=kbuild-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox