From: "Eric S. Raymond" <esr@thyrsus.com>
To: CML2 <linux-kernel@vger.kernel.org>, kbuild-devel@lists.sourceforge.net
Cc: torvalds@transmeta.com, laughing@shared-source.org
Subject: Configure.help is complete
Date: Thu, 31 May 2001 13:24:54 -0400 [thread overview]
Message-ID: <20010531132454.A8361@thyrsus.com> (raw)
It gives me great pleasure to announce that the Configure.help master
file is now complete with respect to 2.4.5. Every single one of the
2699 configuration symbols actually used in the 2.4.5 codebase's C
source files or Makefiles now has an entry in Configure.help.
This does not, of course, mean the job of maintaining Configure.help
is done; symbols will be added and dropped in the future (there are a
handful of new ones in ac5, all now documented), and some existing
entries could stand to be rewritten and expanded. But we have passed
a milestone -- maintainance will now be a matter of keeping the boat
bailed rather than trying to ignore a hole in the side.
Thanks to all the contributors who helped put together the over 550
entries necessary to catch up, too many to name here. The result
is available at:
http://www.tuxedo.org/~esr/cml2/Configure.help.gz
Though carried on the CML2 project page, it can be used with CML1 and
is current with respect to both Linus's tree and Alan's.
I now have two requests of Linus and Alan:
1. Please pick up this work now. It is a really substantial improvement
on what you have in your trees, incorporating it cannot break anything,
and you'll help prevent unnecessary hassles due to clashing patches
in the future.
2. Please make a policy of rejecting patches that add new configuration
symbols without also adding an explanatory Configure.help entry --
and please *announce* that you will do so. We can raise our standards
now, and for the sake of having a well-documentated kernel and
configuration system I submit that we ought to.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Never could an increase of comfort or security be a sufficient good to be
bought at the price of liberty.
-- Hillaire Belloc
next reply other threads:[~2001-05-31 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-31 17:24 Eric S. Raymond [this message]
2001-05-31 20:13 ` Configure.help is complete José Luis Domingo López
2001-05-31 18:23 ` Eric S. Raymond
2001-05-31 18:21 ` Alan Cox
2001-06-01 1:50 ` José Luis Domingo López
2001-05-31 19:48 ` Arjan van de Ven
2001-05-31 19:57 ` Alexander Viro
2001-06-01 12:43 ` Phil Auld
2001-06-01 12:59 ` David Weinehall
2001-06-01 15:45 ` Jonathan Lundell
2001-06-02 18:27 ` Remi Turk
2001-05-31 22:56 ` Nerijus Baliunas
-- strict thread matches above, loose matches on Subject: below --
2001-05-31 20:12 BH
2001-05-31 20:42 ` Arjan van de Ven
2001-05-31 20:50 ` Eric S. Raymond
2001-05-31 21:22 ` Alan Cox
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=20010531132454.A8361@thyrsus.com \
--to=esr@thyrsus.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=laughing@shared-source.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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