From: Russell King <rmk@arm.linux.org.uk>
To: "Eric S. Raymond" <esr@thyrsus.com>,
linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: Cross-referencing frenzy
Date: Thu, 19 Apr 2001 09:02:20 +0100 [thread overview]
Message-ID: <20010419090220.A2291@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20010418233445.A28628@thyrsus.com>
In-Reply-To: <20010418233445.A28628@thyrsus.com>; from esr@thyrsus.com on Wed, Apr 18, 2001 at 11:34:45PM -0400
On Wed, Apr 18, 2001 at 11:34:45PM -0400, Eric S. Raymond wrote:
> Especially look for CONFIG_* symbols that only occur in .c or .h files.
> I think almost every one of those lines represents a bug that needs to be
> fixed.
It'd be easier to read if they were alphanumerically sorted.
The ones that show up in arch/arm/def-configs are purely because I've been
keeping back the updates to these files; each time the config structure
changes, I get a nice big patch from people with the new def-configs. I
didn't want to inflict this too regularly on people.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-04-19 8:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 3:34 Cross-referencing frenzy Eric S. Raymond
2001-04-19 4:00 ` Richard Gooch
2001-04-19 4:11 ` Rik van Riel
2001-04-19 4:36 ` Edward S. Marshall
2001-04-19 5:06 ` Richard Gooch
2001-04-19 5:37 ` Eric S. Raymond
2001-04-19 9:26 ` Rogier Wolff
2001-04-19 13:36 ` [kbuild-devel] " Eric S. Raymond
2001-04-19 15:22 ` Rogier Wolff
2001-04-19 5:38 ` Jeff Garzik
2001-04-19 5:32 ` Eric S. Raymond
2001-04-19 11:41 ` Alan Cox
2001-04-19 4:49 ` Andreas Dilger
2001-04-19 13:23 ` Mike Castle
2001-04-19 13:36 ` Alan Cox
2001-04-19 17:33 ` Eric S. Raymond
2001-04-19 20:53 ` Jim Treadway
2001-04-19 8:02 ` Russell King [this message]
2001-04-19 13:16 ` Eric S. Raymond
2001-04-19 14:17 ` Jeff Garzik
2001-04-19 14:25 ` Eric S. Raymond
2001-04-19 18:49 ` [kbuild-devel] " Peter Samuelson
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=20010419090220.A2291@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=esr@thyrsus.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox