public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Nicolas Pitre <nico@cam.org>
Cc: CML2 <linux-kernel@vger.kernel.org>, kbuild-devel@lists.sourceforge.net
Subject: Re: Missing help entries in 2.4.6pre5
Date: Thu, 21 Jun 2001 22:15:51 -0400	[thread overview]
Message-ID: <20010621221551.A9839@thyrsus.com> (raw)
In-Reply-To: <20010621154934.A6582@thyrsus.com> <Pine.LNX.4.33.0106211812560.30096-100000@xanadu.home>
In-Reply-To: <Pine.LNX.4.33.0106211812560.30096-100000@xanadu.home>; from nico@cam.org on Thu, Jun 21, 2001 at 06:22:22PM -0400

Nicolas Pitre <nico@cam.org>:
> > CONFIG_XSCALE_IQ80310
> 
> 1- This symbol is mine;
> 2- It is part of 2.4.6-pre5 only as a dependency argument, with no
>    point where a value is actually assigned to it;
> 3- It is likely to be different when the actual question for which the
>    user need an help text is merged into the mainline kernel.
> 
> So you can safely ignore it for now.

I've put it on my ignore list.
 
> Maybe it could be a good thing for your tool to ignore missing help text for
> symbols that don't get enabled interactively by the user?

It already does that for derivations (in CML1, define_*).  The real problem 
here is that my report generators aren't smart enough to tell when a CML1
symbol is referenced in a CML1 config but never set.  That problem could be
solved, but it's unusual that I don't think it's worth the effort.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

The day will come when the mystical generation of Jesus by the Supreme
Being as his father, in the womb of a virgin, will be classed with the
fable of the generation of Minerva in the brain of Jupiter.
	-- Thomas Jefferson, 1823

  parent reply	other threads:[~2001-06-22  2:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010622111154.A13799@thyrsus.com>
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
2001-06-22 13:51         ` Eric S. Raymond
2001-06-22  2:15     ` Eric S. Raymond [this message]
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=20010621221551.A9839@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@cam.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