From: Valdis.Kletnieks@vt.edu
To: nir.tzachar@gmail.com
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
sam@ravnborg.org, zippel@linux-m68k.org, andi@firstfloor.org
Subject: Re: [PATCH] nconfig v5
Date: Fri, 06 Nov 2009 11:04:59 -0500 [thread overview]
Message-ID: <4185.1257523499@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 06 Nov 2009 10:36:54 +0200." <1257496614-12052-1-git-send-email-nir.tzachar@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 628 bytes --]
On Fri, 06 Nov 2009 10:36:54 +0200, nir.tzachar@gmail.com said:
> Building on menuconfig, this patch implements a more modern look interface using
> ncurses and ncurses' satellite libraries (menu, panel, form).
What is the minimum release of ncurses needed? Some of us silverbacks have
bad memories of twisty little mazes of ncurses releases, all incompatible. ;)
(Much less of an issue if we're only trying to build on Linux - but at least
in the semi-recent past we've supported doing a kernel build on non-Linux
boxes. Did that get lopped out at some point, or do we need to worry about
what ncurses Solaris ships with?)
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2009-11-06 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 8:36 [PATCH] nconfig v5 nir.tzachar
2009-11-06 10:20 ` Frans Pop
2009-11-06 16:04 ` Valdis.Kletnieks [this message]
2009-11-06 18:52 ` Nir Tzachar
2009-11-06 19:12 ` Randy Dunlap
2009-11-07 1:07 ` Randy Dunlap
2009-11-07 14:07 ` [PATCH] nconfig v6 nir.tzachar
2009-11-07 22:10 ` Ben Nizette
2009-11-25 10:28 ` [PATCH] nconfig v7 nir.tzachar
2009-11-30 14:40 ` Michal Marek
2009-11-30 16:34 ` Nir Tzachar
-- strict thread matches above, loose matches on Subject: below --
2009-11-06 14:39 [PATCH] nconfig v5 nir.tzachar
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=4185.1257523499@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=andi@firstfloor.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nir.tzachar@gmail.com \
--cc=sam@ravnborg.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