From: Jeff Garzik <garzik@havoc.gtf.org>
To: Patrick Mauritz <oxygene@studentenbude.ath.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Configure.help in 2.5.3-pre6
Date: Wed, 30 Jan 2002 03:22:02 -0500 [thread overview]
Message-ID: <20020130032202.F32317@havoc.gtf.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0201292147530.22800-100000@barbarella.hawaga.org.uk> <1012370595.3392.21.camel@phantasy> <a3847v$17m$1@penguin.transmeta.com> <20020130075444.GA401@hydra>
In-Reply-To: <20020130075444.GA401@hydra>; from oxygene@studentenbude.ath.cx on Wed, Jan 30, 2002 at 08:54:44AM +0100
On Wed, Jan 30, 2002 at 08:54:44AM +0100, Patrick Mauritz wrote:
> short being between now and the cml2 inclusion?
CML2 is butt-ugly to read and maintain, at least for drivers. It is
my hope that Eric will take input that will make CML2 more readable
and useable by kernel hackers.
The current config language, for all the flaws CML2 proponents love to
point out, is quite readable and understandable. It doesn't force
the entire domain of CONFIG_xxx symbols on you, like CML2 does.
[Unless this has changed recently] CML2 forces architecture X to be
mindful of changes in architecture Y. For some tasks this make sense,
but for other cases this is a completely needless usurpation of an
architecture's control of the CONFIG_xxx namespace. The current
config language allows an arch to -control- the namespace, while
CML2 appears to reduce flexibility by requiring global instead of
arch-specific control of the namespace.
It is my hope that some sort of compromise can be found... :(
Jeff
next prev parent reply other threads:[~2002-01-30 8:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 5:51 Ben Clifford
2002-01-30 6:03 ` Robert Love
2002-01-30 6:35 ` Linus Torvalds
2002-01-30 7:54 ` Patrick Mauritz
2002-01-30 8:22 ` Jeff Garzik [this message]
2002-01-30 7:11 ` Robert Love
2002-01-30 8:20 ` David Lang
2002-02-07 9:24 ` Thomas Capricelli
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=20020130032202.F32317@havoc.gtf.org \
--to=garzik@havoc.gtf.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oxygene@studentenbude.ath.cx \
/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
Powered by JetHome