mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Jeff Mahoney <jeffm@suse.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Roman Zippel <zippel@linux-m68k.org>,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] Add ``cloneconfig'' target
Date: Sun, 27 Feb 2011 19:44:53 +0100	[thread overview]
Message-ID: <20110227184453.GA28732@merkur.ravnborg.org> (raw)
In-Reply-To: <AANLkTikigj1rDHrUaySHAYrW=GPPezbmcaDfx78AqE1_@mail.gmail.com>

On Sat, Feb 26, 2011 at 06:28:43PM -0500, Arnaud Lacombe wrote:
> Hi,
> 
> On Sat, Feb 26, 2011 at 6:03 PM, Arnaud Lacombe <lacombar@gmail.com> wrote:
> >> The fact that the configuration is gzipped does not warrant
> >> a new option to deal with this that almost duplicate the
> >> existing functionality.
> >>
> > agree.
> >
> Let me precise, as there may be confusion. I agree about the new
> target issue, but definitively think this kconfig "option" (more a
> hack, which required a special option within kconfig) should be
> handled by Kbuild, not Kconfig, ie. I'd discard "option
> defconfig_list". File decompression (and eventually which config to
> pick) should be done prior to the invocation of Kconfig.

If you can come up with something simpler and better than
what we have today then fine.
Simplifying kconfgi would be good.

But at least barebox uses defconfig_list - an maybe others.
We need to consider non-kernel users too.

	Sam

  reply	other threads:[~2011-02-27 18:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25  2:35 Jeff Mahoney
2011-02-25  6:07 ` Sam Ravnborg
2011-02-26  0:44   ` [PATCH 1/2] kconfig: add support for type handlers Jeff Mahoney
2011-02-26  1:28     ` Arnaud Lacombe
2011-02-26 17:27       ` Jeff Mahoney
2011-02-26  0:44   ` [PATCH 2/2] kconfig: Use /proc/config.gz as a configuration source Jeff Mahoney
2011-02-26 19:47   ` [PATCH] Add ``cloneconfig'' target Arnaud Lacombe
2011-02-26 22:18     ` Sam Ravnborg
2011-02-26 23:03       ` Arnaud Lacombe
2011-02-26 23:28         ` Arnaud Lacombe
2011-02-27 18:44           ` Sam Ravnborg [this message]
2011-02-27  9:03       ` Geert Uytterhoeven
2011-02-27 17:13         ` Arnaud Lacombe
2011-02-27 17:54         ` Jeff Mahoney
2011-02-26 22:47     ` Miguel Ojeda
2011-02-26 22:57       ` Arnaud Lacombe
2011-02-26 23:16         ` Miguel Ojeda
2011-02-26 23:26           ` Arnaud Lacombe
2011-02-26 23:38             ` Jeff Mahoney
2011-02-26 23:50               ` Arnaud Lacombe
2011-02-26 23:34         ` Jeff Mahoney
2011-02-26 23:53           ` Arnaud Lacombe
2011-02-26 19:50 ` Arnaud Lacombe

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=20110227184453.GA28732@merkur.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=jeffm@suse.com \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®