From: David Woodhouse <dwmw2@infradead.org>
To: esr@thyrsus.com
Cc: Russell King <rmk@arm.linux.org.uk>, Nicolas Pitre <nico@cam.org>,
CML2 <linux-kernel@vger.kernel.org>,
kbuild-devel@lists.sourceforge.net
Subject: Re: Missing help entries in 2.4.6pre5
Date: Fri, 22 Jun 2001 09:24:32 +0100 [thread overview]
Message-ID: <8226.993198272@redhat.com> (raw)
In-Reply-To: <20010621185144.A8669@thyrsus.com>
In-Reply-To: <20010621185144.A8669@thyrsus.com> <20010621154934.A6582@thyrsus.com> <Pine.LNX.4.33.0106211812560.30096-100000@xanadu.home> <20010621234002.Z18978@flint.arm.linux.org.uk>
esr@thyrsus.com said:
> I've done that in my rulesfile, thanks. Here is the current list of
> ignored symbols:
> derive CMDLINE_BOOL from n
....etc...
That'll nicely break oldconfig behaviour when the options in question do
get merged into the main tree, won't it?
Can you make them optional instead? So for normal users they're still
_really_ undefined, and hence get asked about when they appear, rather than
defaulting to 'n'.
--
dwmw2
next prev parent reply other threads:[~2001-06-22 8:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 19:49 Missing help entries in 2.4.6pre5 Eric S. Raymond
2001-06-21 19:55 ` Russell King
2001-06-21 20:03 ` Eric S. Raymond
2001-06-22 8:13 ` David Woodhouse
2001-06-22 13:49 ` Eric S. Raymond
2001-06-22 13:47 ` Russell King
2001-06-22 13:54 ` Eric S. Raymond
2001-06-22 13:54 ` Russell King
2001-06-22 14:28 ` Brent D. Norris
2001-06-22 14:00 ` Wichert Akkerman
2001-06-22 14:13 ` Rob Landley
2001-06-24 0:05 ` David Woodhouse
2001-06-22 15:43 ` Alan Cox
2001-06-22 16:01 ` Eric S. Raymond
2001-06-22 13:56 ` David Woodhouse
2001-06-22 14:24 ` Eric S. Raymond
2001-06-22 14:54 ` David Woodhouse
2001-06-22 16:27 ` David Woodhouse
2001-06-22 17:12 ` Eric S. Raymond
2001-06-21 22:22 ` Nicolas Pitre
2001-06-21 22:40 ` Russell King
2001-06-21 22:51 ` Eric S. Raymond
2001-06-22 8:24 ` David Woodhouse [this message]
2001-06-22 13:51 ` Eric S. Raymond
2001-06-22 2:15 ` Eric S. Raymond
2001-06-22 14:47 Holzrichter, Bruce
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=8226.993198272@redhat.com \
--to=dwmw2@infradead.org \
--cc=esr@thyrsus.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.org \
--cc=rmk@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).