[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100729081316.GA4990@merkur.ravnborg.org>
Date: Thu, 29 Jul 2010 10:13:16 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Michal Marek <mmarek@...e.cz>
Cc: lkml <linux-kernel@...r.kernel.org>,
linux-kbuild <linux-kbuild@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Roman Zippel <zippel@...ux-m68k.org>,
Uwe Kleine-Koig <u.kleine-koenig@...gutronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Aristeu Rozanski <aris@...hat.com>
Subject: Re: [RFC PATCH] kconfig: use long options in conf
On Wed, Jul 28, 2010 at 10:36:22PM +0200, Sam Ravnborg wrote:
> Hi Michal.
>
> I cooked up the following to introduce long options in conf.
> But in the process I dropped the short options. Is this OK?
On top of this patch I did another two.
They fixup the *nonint_oldconfig targets:
nonint_oldconfig:
- renamed to listnewconfig
- print new options to stdout (to better support redirect)
- no longer saves a new configuration
- does ot exist with a failure code if there is new options
loose_noninit_oldconfig:
- renamed to oldnoconfig
- does ot exist with a failure code if there is new options
This is a lot cleaner and much more sensible names.
And they still support the suecase where they
list new options and can set them to n per default.
[cc: list trimmed on patches]
Sam
Sam Ravnborg (2):
kconfig: rename loose_nonint_oldconfig => oldnoconfig
kconfig: change nonint_oldconfig to listnewconfig
scripts/kconfig/Makefile | 12 +++++-------
scripts/kconfig/conf.c | 46 +++++++++++++++++-----------------------------
2 files changed, 22 insertions(+), 36 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists