From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: linux kernel conf 0.5
Date: Tue, 10 Sep 2002 19:44:52 -0400 [thread overview]
Message-ID: <3D7E83F4.6050302@mandrakesoft.com> (raw)
In-Reply-To: 3D7E7D5F.F37D2D49@linux-m68k.org
Roman Zippel wrote:
> 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.
[...]
> 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.
How about posting a kernel patch (or link to one) that you feel is
suitable for 2.5.x integration? That makes it a bit easier to review in
context, and may help to resolve any final integration issues.
For the record I like what I've seen so far...
Jeff
next prev parent reply other threads:[~2002-09-10 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 23:16 linux kernel conf 0.5 Roman Zippel
2002-09-10 23:44 ` Jeff Garzik [this message]
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=3D7E83F4.6050302@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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