From: "Eric S. Raymond" <esr@thyrsus.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: CML2 <linux-kernel@vger.kernel.org>, kbuild-devel@lists.sourceforge.net
Subject: Re: Dead symbol elimination, stage 1
Date: Thu, 19 Apr 2001 13:59:55 -0400 [thread overview]
Message-ID: <20010419135955.A3841@thyrsus.com> (raw)
In-Reply-To: <20010419131944.A3049@thyrsus.com> <20010419184444.A3111@flint.arm.linux.org.uk>
In-Reply-To: <20010419184444.A3111@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Thu, Apr 19, 2001 at 06:44:44PM +0100
Russell King <rmk@arm.linux.org.uk>:
> On Thu, Apr 19, 2001 at 01:19:44PM -0400, Eric S. Raymond wrote:
> > The following patch cleans dead symbols out of the defconfigs in the 2.4.4pre4
> > source tree. It corrects a typo involving CONFIG_GEN_RTC. Another typo
> > involving CONFIG_SOUND_YMPCI doesn't need to be corrected, as the symbol
> > is never set in these files.
>
> As I said previously, please don't eliminate the ones on arch/arm -
> you'll prevent me from sending a patch to Alan without a _lot_ more
> work.
Um...this is what you said:
> 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.
I read this as "I haven't fixed the problem because..." not as "Don't
fix the problem." Please be more explicit next time so I won't step on
your toes?
I don't care whether it's you or me that cleans up this part of the
dead-symbol mess. I'm just trying to get it cleaned up.
I'm rather disturbed by the amount of crap kxref is turning up -- I
expected dozens of dodgy bits, but I'm finding hundreds. We need to pay
better attention to janitorial issues like this if the kernel code
isn't going to degenerate into an unmaintainable hairball.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
False is the idea of utility that sacrifices a thousand real advantages for
one imaginary or trifling inconvenience; that would take fire from men because
it burns, and water because one may drown in it; that has no remedy for evils
except destruction. The laws that forbid the carrying of arms are laws of
such a nature. They disarm only those who are neither inclined nor determined
to commit crimes.
-- Cesare Beccaria, as quoted by Thomas Jefferson's Commonplace book
next prev parent reply other threads:[~2001-04-19 17:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 17:19 Dead symbol elimination, stage 1 Eric S. Raymond
2001-04-19 17:44 ` Russell King
2001-04-19 17:59 ` Eric S. Raymond [this message]
2001-04-19 19:36 ` rmk
2001-04-19 20:04 ` rmk
2001-04-19 21:15 ` David Woodhouse
2001-04-19 18:05 ` David Woodhouse
2001-04-19 18:14 ` Eric S. Raymond
2001-04-20 6:33 ` Eyal Lebedinsky
2001-04-19 17:48 ` David Woodhouse
2001-04-19 18:06 ` Eric S. Raymond
2001-04-19 21:06 ` [kbuild-devel] " Kai Germaschewski
2001-04-21 11:46 ` Armin Schindler
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=20010419135955.A3841@thyrsus.com \
--to=esr@thyrsus.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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