From: Adrian Bunk <bunk@stusta.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] how do config options disappear from the "defconfig" files?
Date: Fri, 16 Feb 2007 17:21:31 +0000 [thread overview]
Message-ID: <20070216172131.GP13958@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0702160939220.29917@CPE00045a9c397f-CM001225dbafb6>
On Fri, Feb 16, 2007 at 09:40:46AM -0500, Robert P. J. Day wrote:
>
> i just want to clarify one point about all of the defconfig files in
> the source tree. if a CONFIG option is removed from the Kconfig
> infrastructure, does that corresponding entry eventually disappear
> from all of the defconfig files based on an automatic build at some
> point? thanks.
Not automatically.
Architecture maintainers sometimes [1] update the defconfig files for
their architectures.
But don't bother - a dead option in a defconfig file doesn't do any
harm, and manually removing options from defconfig files only causes
never ending patch conflicts.
> rday
cu
Adrian
[1] in practice, some do it often and some never
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2007-02-16 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 14:40 [KJ] how do config options disappear from the "defconfig" files? Robert P. J. Day
2007-02-16 17:10 ` Oleg Verych
2007-02-16 17:21 ` Adrian Bunk [this message]
2007-02-16 18:02 ` Robert P. J. Day
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=20070216172131.GP13958@stusta.de \
--to=bunk@stusta.de \
--cc=kernel-janitors@vger.kernel.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.