From: "Eric S. Raymond" <esr@thyrsus.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: 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 10:24:58 -0400 [thread overview]
Message-ID: <20010622102458.A13435@thyrsus.com> (raw)
In-Reply-To: <20010622094934.A13075@thyrsus.com> <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> <10604.993218210@redhat.com>
In-Reply-To: <10604.993218210@redhat.com>; from dwmw2@infradead.org on Fri, Jun 22, 2001 at 02:56:50PM +0100
David Woodhouse <dwmw2@infradead.org>:
> The irritation only happened because you seem to have ignored the remainder
> of my original response and patch - which explained the status of the Ocelot
> and XScale options, and which removed the other offending option from
> Config.in completely. I'd removed the corresponding code before syncing up
> with Linus because it wanted rewriting before it could be submitted, just
> forgotten to remove the config option for it.
No, I remember that. But if I don't remind lkml periodically that there is
work not done on this, I fear it will slide to the bottom of peoples'
to-do lists and fall off. That's how we got to the distressing state where
about 1/4 of the configuration symbols weren't documented.
I solved this problem by (a) working like a dog at writing help
entries myself, and (b) using a combination of supplication and
irritation on configuration maintainers to get them to hold up their
end. This was effective; we've gone from 537 undocumented symbols to 2.
In any situation like this, supplication tends to work well initially;
you catch the cooperative people who would almost have done what you
needed anyway, which is usually 60% or more of them. As you get
towards the bottom of the barrel, (subtle) irritation becomes more
important. While it isn't *necessarily* the case that the last few
holdouts won't move unless you're a persistent pain in the butt about
it, that's the smart way to bet.
(I've done jobs like this before. Couldn't you tell? :-))
> I'm already rejecting patches which add new config entries but don't add
> the corresponding help text. What more do you want?
That's very good, and I thank you for that policy. From *you*, I don't
want anything else. From the person(s) reponsible for the missing symbols,
I want documentation. The problem is that, lacking a detailed database
of who is responsible for what, I don't know how to prod each of the
people I really want to supplicate/irritate without having you see it
also.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Rifles, muskets, long-bows and hand-grenades are inherently democratic
weapons. A complex weapon makes the strong stronger, while a simple
weapon -- so long as there is no answer to it -- gives claws to the
weak.
-- George Orwell, "You and the Atom Bomb", 1945
next prev parent reply other threads:[~2001-06-22 14:27 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 [this message]
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=20010622102458.A13435@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.