From: Matt Mackall <mpm@selenic.com>
To: Rob Landley <rob@landley.net>
Cc: Roman Zippel <zippel@linux-m68k.org>,
linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] Start to genericize kconfig for use by other projects.
Date: Thu, 12 Jul 2007 18:16:45 -0500 [thread overview]
Message-ID: <20070712231645.GY11166@waste.org> (raw)
In-Reply-To: <200707121444.18599.rob@landley.net>
On Thu, Jul 12, 2007 at 02:44:18PM -0400, Rob Landley wrote:
> On Thursday 12 July 2007 12:28:39 pm Roman Zippel wrote:
> > Hi,
> >
> > On Wed, 11 Jul 2007, Rob Landley wrote:
> > > Replace name "Linux Kernel" in menuconfig with a macro (defaulting to
> > > "Linux Kernel" if not -Ddefined by the makefile), and remove a few
> > > unnecessary occurrences of "kernel" in pop-up text.
> >
> > Could you drop the PROJECT_NAME changes for now? The rest looks fine.
> > I would prefer if the project would be settable via Kconfig.
>
> Are projects likely to grab a common kconfig binary externally, rather
> than build their own?
Yes.
If you really want to share kconfig, it'd be better to break it off
into a separately packaged project. For the time being, the kernel
makefiles can look for it in path, then fall back to its own copy
which we can eventually drop.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2007-07-12 23:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 19:22 [PATCH] Start to genericize kconfig for use by other projects Rob Landley
2007-07-11 19:55 ` Adrian Bunk
2007-07-11 21:18 ` Rob Landley
2007-07-12 23:35 ` Adrian Bunk
2007-07-12 16:28 ` Roman Zippel
2007-07-12 17:00 ` Roman Zippel
2007-07-12 18:44 ` Rob Landley
2007-07-12 23:16 ` Matt Mackall [this message]
2007-07-13 17:19 ` Rob Landley
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=20070712231645.GY11166@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--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