public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	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: Sat, 26 Feb 2011 18:34:09 -0500	[thread overview]
Message-ID: <4D698DF1.7060303@suse.com> (raw)
In-Reply-To: <AANLkTi=bJRh=0N6wP3LJWTQHSXsX4xdE7oOzK0CFcTfc@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/26/2011 05:57 PM, Arnaud Lacombe wrote:
> Hi,
> 
> On Sat, Feb 26, 2011 at 5:47 PM, Miguel Ojeda
> <miguel.ojeda.sandonis@gmail.com> wrote:
>> On Sat, Feb 26, 2011 at 8:47 PM, Arnaud Lacombe <lacombar@gmail.com> wrote:
>>> Why ? Thing should be kept simple. kconfig's job is not to know about
>>> the trillion file format which exist in the world, even more if the
>>> implementation is made by building a command[0], executing it in a
>>> separate process and reading the output. This is the shell's job. What
>>> may be useful in the contrary would be to eventually teach kconfig to
>>> read from <stdin>.
>>
>> /proc/config.gz is provided by the kernel and its format is defined by
>> kconfig itself which is, as well, part of the kernel (it is not one
>> random format from a pool of a trillion), so it will be nice if
>> kconfig learns how to read its own configuration from there.
>>
> your point being ? kconfig is not only used by the Linux kernel, and
> you cannot expect the feature to only be used in the cozy Linux kernel
> environment.

But this argument isn't really relevant. As with all of the other files
listed in the defconfig_list, if it's missing (or can't be read), it
will move on to the next one. Decompressing it first just makes things
/more/ confusing since the initial message of 'defaults read from...'
will read the name of the decompressed temporary file, not the source.
It makes more sense to see it as "reading defaults from /proc/config.gz
since that's obvious to anyone with kernel experience.

- -Jeff

- -- 
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAk1pjfEACgkQLPWxlyuTD7Ki0wCfU8KrumyxlD+qTFajlhc1eHOn
rMoAn0PqPyBYhBWlFTBT8YaL8/MWjw1J
=PVwv
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2011-02-26 23:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25  2:35 [PATCH] Add ``cloneconfig'' target 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
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 [this message]
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=4D698DF1.7060303@suse.com \
    --to=jeffm@suse.com \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --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