From: Roman Zippel <zippel@linux-m68k.org>
To: linux-kernel <linux-kernel@vger.kernel.org>,
kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: linux kernel conf 0.5
Date: Wed, 11 Sep 2002 01:16:47 +0200 [thread overview]
Message-ID: <3D7E7D5F.F37D2D49@linux-m68k.org> (raw)
Hi,
At http://www.xs4all.nl/~zippel/lc/lkc-0.5.tar.gz you can find the
latest version of the new config system. Besides various small bug
fixes, it includes the following changes:
- Improved mouse interface of qconf
- qconf isn't build if QT isn't available
- "if" ... "endif" block added
- update to 2.5.35
With the exception of the X interface I'm not planning any big visible
changes anymore, so slowly I'd like to know any reason, why this config
system shouldn't go into 2.5.x. The old arguments against cml2 don't
really work anymore, so you have to come up with something new. :-)
The only argument I know of is that various people on kbuild mailing
list are afraid, that Linus wouldn't accept such a big change. I think
hardly anyone cares how the config backend is implemented, so the only
really visible change is the new config format, but here only the format
is new, the information is still the same (if anyone cares about the
subtle differences, I can explain them separately). Making a clear cut
now is really the easiest solution. Changing parsers and syntax
separately would be more painful, as we risks constants subtle behaviour
changes and bugs during this period, by doing a single switch we can
quickly get over it.
Otherwise the little feedback I got was mostly positive, so if anything
thinks the old config system is in any way better, I'd really like to
know about it now (and if anyone wants to keep the old system, (s)he
just volunteered to fix all the subtle differences between the three
different parsers). So unless I hear objections rather soon, it's up to
Linus.
bye, Roman
next reply other threads:[~2002-09-10 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 23:16 Roman Zippel [this message]
2002-09-10 23:44 ` linux kernel conf 0.5 Jeff Garzik
2002-09-11 0:20 ` Roman Zippel
2002-09-11 11:17 ` Sam Ravnborg
2002-09-11 11:51 ` Roman Zippel
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=3D7E7D5F.F37D2D49@linux-m68k.org \
--to=zippel@linux-m68k.org \
--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