From: Sam Ravnborg <sam@ravnborg.org>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Roman Zippel <zippel@linux-m68k.org>,
"Elyse M. Grasso" <emgrasso@data-raptors.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Eric Van Hensbergen <ericvh@gmail.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
kbuild-devel@lists.sourceforge.net,
Andreas Herrmann <aherrman@arcor.de>
Subject: Re: A bit of kconfig rewrite (Re: [PATCH] 9p: fix compile error if !CONFIG_SYSCTL)
Date: Sat, 6 Oct 2007 20:59:20 +0200 [thread overview]
Message-ID: <20071006185920.GA8005@uranus.ravnborg.org> (raw)
In-Reply-To: <20071006175145.GD22435@flower.upol.cz>
> Maintenance and acceptance of the m4/make/perl/C/ncurses community of my
> mainly `TERM=linux ; sed && sh' approach is more important for me.
There is noone having trouble with ncurses dependency today.
And perl is not yet mandatory for a kernel build expect
for a few architectures.
m4 is not used by the kernel - to my best knowledge.
Sam
next prev parent reply other threads:[~2007-10-06 18:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 8:05 [PATCH] 9p: fix compile error if !CONFIG_SYSCTL Andreas Herrmann
2007-09-18 18:53 ` roel
2007-09-18 20:15 ` Andreas Herrmann
2007-09-20 6:31 ` Andrew Morton
2007-09-20 7:23 ` Andreas Herrmann
2007-09-27 21:40 ` Nick Piggin
2007-09-28 14:34 ` Linus Torvalds
2007-09-28 0:05 ` Nick Piggin
2007-09-28 17:11 ` Arjan van de Ven
2007-09-28 17:12 ` Elyse M. Grasso
2007-10-01 7:27 ` A bit of kconfig rewrite (Re: [PATCH] 9p: fix compile error if !CONFIG_SYSCTL) Oleg Verych
2007-10-01 8:05 ` Sam Ravnborg
2007-10-01 12:53 ` Elyse M. Grasso
2007-10-05 2:35 ` [kbuild-devel] " Roman Zippel
2007-10-06 15:26 ` Oleg Verych
2007-10-06 16:03 ` Linus Torvalds
2007-10-06 17:51 ` Oleg Verych
2007-10-06 18:59 ` Sam Ravnborg [this message]
2007-10-06 20:47 ` Oleg Verych
2007-10-06 21:10 ` Sam Ravnborg
2007-10-06 22:07 ` Oleg Verych
2007-10-07 9:49 ` Geert Uytterhoeven
2007-10-08 20:22 ` Sam Ravnborg
2007-10-08 21:25 ` Oleg Verych
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=20071006185920.GA8005@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=aherrman@arcor.de \
--cc=akpm@linux-foundation.org \
--cc=emgrasso@data-raptors.com \
--cc=ericvh@gmail.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=olecom@flower.upol.cz \
--cc=torvalds@linux-foundation.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
Powered by JetHome