mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: Romain Lievin <roms@tilp.info>
Subject: [PATCH] kconfig update
Date: Sun, 9 Mar 2003 04:57:54 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0303090432200.32518-100000@serv> (raw)

Hi,

It took a bit longer than I wanted, but here is finally another kconfig 
update. There are two important changes: I included Romain's gtk front 
end and the support for the menuconfig keyword. Unfortunately the first is 
lacking a bit support for the latter. Romain, you have to check that menu 
entries of type P_MENU can now also have a config symbol. I looked a bit 
at it myself but my gtk knowledge is insufficient. :)
Other changes are small parser fixes and the config list in qconf has a 
parent entry, so it should be more obvious, how to get to a parent menu.
I don't expect bigger problems, so I want to send this patch soon to 
Linus.
The patch is at http://www.xs4all.nl/~zippel/lc/patches/kconfig-2.5.64.diff

bye, Roman


             reply	other threads:[~2003-03-09  3:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09  3:57 Roman Zippel [this message]
2003-03-09  8:59 ` Christoph Hellwig
2003-03-09 12:14   ` Petr Baudis
2003-03-09 12:46 ` Roman Zippel
2003-03-09 19:01 ` Sam Ravnborg
2003-03-09 19:30   ` Roman Zippel
2003-03-09 19:34     ` Sam Ravnborg
2003-03-09 20:18       ` Roman Zippel
2003-03-09 21:15         ` Sam Ravnborg
2003-03-10 10:00           ` Roman Zippel
2003-03-10 19:12             ` Sam Ravnborg
     [not found] ` <20030314144329.GA2768@wanadoo.fr>
     [not found]   ` <Pine.LNX.4.44.0303141602330.5042-100000@serv>
2003-03-14 19:36     ` [PATCH] kconfig update, GTK+ updated Romain Lievin
2003-05-28 22:59 [PATCH] kconfig update 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=Pine.LNX.4.44.0303090432200.32518-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roms@tilp.info \
    /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

all inboxes | Powered by JetHome®