mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Engelhardt <jengelh@computergmbh.de>, Rob Landley <rob@landley.net>
Cc: zippel@linux-m68k.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	randy.dunlap@oracle.com
Subject: Re: [PATCH] Allow kconfig to accept overrides
Date: Tue, 16 Oct 2007 06:29:58 +0200	[thread overview]
Message-ID: <20071016042957.GB27909@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0710122341530.16098@fbirervta.pbzchgretzou.qr>

Hi Rob & Jan.

On Fri, Oct 12, 2007 at 11:44:08PM +0200, Jan Engelhardt wrote:
> 
> Allow config variables in .config to override earlier ones in the same
> file. In other words,
> 
> 	# CONFIG_SECURITY is not defined
> 	CONFIG_SECURITY=y
> 
> will activate it. This makes it a bit easier to do
> 
> 	(cat original-config myconfig myconfig2 ... >.config)
> 
> and run menuconfig as expected.


How far is this from the miniconfig functionality?
Is it the same or can we achieve the miniconfig support
by extending Jan's patch?

See: http://lkml.org/lkml/2007/10/12/391

	Sam


  parent reply	other threads:[~2007-10-16  4:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12 21:44 Jan Engelhardt
2007-10-12 21:49 ` Randy Dunlap
2007-10-12 22:10   ` Jan Engelhardt
2007-10-12 22:57 ` Randy Dunlap
2007-10-12 23:29   ` Jan Engelhardt
2007-10-12 23:32     ` Randy Dunlap
2007-10-13  8:16     ` Stefan Richter
2007-10-13 11:39       ` Jan Engelhardt
2007-10-13 14:01         ` Stefan Richter
2007-10-13 14:15           ` Jan Engelhardt
2007-10-13 16:25             ` Randy Dunlap
2007-10-13 16:36               ` Jan Engelhardt
2007-10-18 13:29                 ` Sam Ravnborg
2007-10-18 13:31                   ` Jan Engelhardt
2007-10-16  4:29 ` Sam Ravnborg [this message]
2007-10-16  5:14   ` Rob Landley
2007-10-16 14:44   ` Jan Engelhardt

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=20071016042957.GB27909@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rob@landley.net \
    --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

all inboxes | Powered by JetHome®