public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, Romain Lievin <roms@tilp.info>
Subject: Re: [PATCH] kconfig update
Date: Sun, 9 Mar 2003 08:59:15 +0000	[thread overview]
Message-ID: <20030309085915.A14548@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0303090432200.32518-100000@serv>; from zippel@linux-m68k.org on Sun, Mar 09, 2003 at 04:57:54AM +0100

On Sun, Mar 09, 2003 at 04:57:54AM +0100, Roman Zippel wrote:
> 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.

Any chance you could take a look at the patch that links lxdialog directly
to menuconfig instead of requiring the separate binary?  It has been
around for a long time and seems like a very worthwhile change, imho.


  reply	other threads:[~2003-03-09  8:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09  3:57 [PATCH] kconfig update Roman Zippel
2003-03-09  8:59 ` Christoph Hellwig [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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=20030309085915.A14548@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roms@tilp.info \
    --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