From: "Eric S. Raymond" <esr@thyrsus.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Woodhouse <dwmw2@infradead.org>,
Russell King <rmk@arm.linux.org.uk>,
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 12:01:50 -0400 [thread overview]
Message-ID: <20010622120150.A14207@thyrsus.com> (raw)
In-Reply-To: <20010622094934.A13075@thyrsus.com> <E15DT5f-0003cG-00@the-village.bc.nu>
In-Reply-To: <E15DT5f-0003cG-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Jun 22, 2001 at 04:43:23PM +0100
Alan Cox <alan@lxorguk.ukuu.org.uk>:
> > 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.
>
> Umm yes so you irritate people and you end up in their killfiles,
> that doesn't strike me as stunningly productive
That's why it's important to be irritating but not obnoxious. The
difference is that between reminding people that there is work to be done
and being insulting about it. Thus, I post lists of symbols for which
there is missing help, but I don't cast aspersions on the people who
haven't come through yet (however tempting that sometimes seems).
I also find it helpful to be up front about *why* I'm being irritating,
just as I'm doing now. When people understand that it's professional
rather than personal, they don't tend to killfile me.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
"To disarm the people... was the best and most effectual way to enslave them."
-- George Mason, speech of June 14, 1788
next prev parent reply other threads:[~2001-06-22 15:58 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 [this message]
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=20010622120150.A14207@thyrsus.com \
--to=esr@thyrsus.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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