public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: David Woodhouse <dwmw2@infradead.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:54:26 -0400	[thread overview]
Message-ID: <20010622095426.C13075@thyrsus.com> (raw)
In-Reply-To: <20010621160309.A6744@thyrsus.com> <20010621154934.A6582@thyrsus.com> <20010621205537.X18978@flint.arm.linux.org.uk> <20010621160309.A6744@thyrsus.com> <7987.993197604@redhat.com> <20010622094934.A13075@thyrsus.com> <20010622144708.D22351@flint.arm.linux.org.uk>
In-Reply-To: <20010622144708.D22351@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Fri, Jun 22, 2001 at 02:47:08PM +0100

Russell King <rmk@arm.linux.org.uk>:
> On Fri, Jun 22, 2001 at 09:49:34AM -0400, Eric S. Raymond wrote:
> > You're a bit irritated.  That's good.  I *want* people who don't write
> > help entries for their configuration symbols to be a bit irritated.
> > That way, they might get around to actually doing what they ought to.
> 
> The people you're irritating are not the people who create these symbols
> though, so its a little pointless.

Irritating port managers a little is good, too.  Sometimes, they can get 
the right person to move.  It's happened before.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

A ``decay in the social contract'' is detectable; there is a growing
feeling, particularly among middle-income taxpayers, that they are not
getting back, from society and government, their money's worth for
taxes paid. The tendency is for taxpayers to try to take more control
of their finances ..
	-- IRS Strategic Plan, (May 1984)

  reply	other threads:[~2001-06-22 13:51 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 [this message]
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
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=20010622095426.C13075@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=dwmw2@infradead.org \
    --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