All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aristeu Rozanski <aris@redhat.com>
To: Michal Marek <mmarek@suse.cz>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Roman Zippel <zippel@linux-m68k.org>,
	Uwe Kleine-Koig <u.kleine-koenig@pengutronix.de>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC PATCH] kconfig: use long options in conf
Date: Thu, 29 Jul 2010 10:47:49 -0400	[thread overview]
Message-ID: <20100729144748.GI6249@redhat.com> (raw)
In-Reply-To: <4C5148A5.10809@suse.cz>

On Thu, Jul 29, 2010 at 11:23:49AM +0200, Michal Marek wrote:
> On 29.7.2010 10:13, Sam Ravnborg wrote:
> > 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
but this kills its usefulness. nonint_oldconfig is used so you can script
the use of a generated configuration (think distro kernel RPMs). if something
is not set, it fails listing what's not set. otherwise it'll save the
configuration and whatever script is using it can proceed.
"listnewconfig" is a new, different target to me.

> > 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.
> 
> I do not object, these new targets are only in the kbuild tree atm, so
> users are not relying on them yet. And the new names indeed describe
> better what they do. Aristeu?
oldnoconfig is fine to me.

-- 
Aristeu


  reply	other threads:[~2010-07-29 14:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-25 21:38 [RFC] kconfig: introduce alldefconfig + savedefconfig Sam Ravnborg
2010-07-25 21:38 ` [PATCH 1/4] kconfig: save location of config symbols Sam Ravnborg
2010-07-25 21:38   ` Sam Ravnborg
2010-07-25 21:39 ` [PATCH 2/4] kconfig: print more info when we see a recursive dependency Sam Ravnborg
2010-07-25 21:39   ` Sam Ravnborg
2010-07-25 21:39 ` [PATCH 3/4] kconfig: add alldefconfig Sam Ravnborg
2010-07-25 21:39   ` Sam Ravnborg
2010-07-25 21:40 ` [PATCH 4/4] kconfig: add savedefconfig Sam Ravnborg
2010-07-25 21:40   ` Sam Ravnborg
2010-07-27 15:42   ` Michal Marek
2010-07-27 16:50     ` Sam Ravnborg
2010-07-28 20:36     ` [RFC PATCH] kconfig: use long options in conf Sam Ravnborg
2010-07-28 20:36       ` Sam Ravnborg
2010-07-29  8:13       ` Sam Ravnborg
2010-07-29  8:15         ` [PATCH 1/2] kconfig: rename loose_nonint_oldconfig => oldnoconfig Sam Ravnborg
2010-07-29  8:15           ` Sam Ravnborg
2010-07-29  8:16         ` [PATCH 2/2] kconfig: change nonint_oldconfig to listnewconfig Sam Ravnborg
2010-07-29  8:16           ` Sam Ravnborg
2010-07-29  9:23         ` [RFC PATCH] kconfig: use long options in conf Michal Marek
2010-07-29 14:47           ` Aristeu Rozanski [this message]
2010-07-29 15:04             ` Michal Marek
2010-07-29 15:16               ` Aristeu Rozanski
2010-07-29 19:34                 ` Sam Ravnborg
2010-07-29 19:50                   ` Aristeu Rozanski
2010-07-29 23:04                     ` Sam Ravnborg
2010-07-30 14:53                       ` Aristeu Rozanski
2010-07-29  9:17       ` Michal Marek
2010-07-29  9:39         ` Sam Ravnborg
2010-07-29 10:08           ` Michal Marek
2010-07-29 14:30             ` Randy Dunlap
2010-07-29 19:29               ` Sam Ravnborg
2010-07-25 22:20 ` [RFC] kconfig: introduce alldefconfig + savedefconfig Sam Ravnborg
2010-07-28  6:47 ` Uwe Kleine-König

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=20100729144748.GI6249@redhat.com \
    --to=aris@redhat.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=sam@ravnborg.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=u.kleine-koenig@pengutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.