All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] how do config options disappear from the "defconfig" files?
Date: Fri, 16 Feb 2007 17:10:03 +0000	[thread overview]
Message-ID: <slrnetbpsv.fkn.olecom@flower.upol.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0702160939220.29917@CPE00045a9c397f-CM001225dbafb6>

> From: "Robert P. J. Day"
> Newsgroups: gmane.linux.kernel.janitors
> Subject: [KJ] how do config options disappear from the "defconfig" files?
> Date: Fri, 16 Feb 2007 09:40:46 -0500 (EST)

>   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.

AFAIK defconfigs are generated and updated by ARCH maintainers.

____


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Kernel-janitor-discuss mailing list
Kernel-janitor-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kernel-janitor-discuss

  reply	other threads:[~2007-02-16 17:10 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 [this message]
2007-02-16 17:21 ` Adrian Bunk
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=slrnetbpsv.fkn.olecom@flower.upol.cz \
    --to=olecom@flower.upol.cz \
    --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.