From: Arjan van de Ven <arjanv@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Configure.help is complete
Date: Thu, 31 May 2001 20:48:44 +0100 [thread overview]
Message-ID: <3B16A01C.ED5C6CCB@redhat.com> (raw)
In-Reply-To: <20010531132454.A8361@thyrsus.com> <20010531201349.B1877@dardhal.mired.net>
José Luis Domingo López wrote:
>
> On Thursday, 31 May 2001, at 13:24:54 -0400,
> Eric S. Raymond wrote:
>
> > 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.
> >
> Would it be great to have a similar documentation for those hundreds of
> "files" under /proc ?. Something like:
<snip>
Powertweak has descriptions for most of the usable /proc entries,
in XML format but the descriptions are easily extractable. Maybe it's
a good idea to make the powertweak set complete instead / share the set
with the kernel docs.
Greetings,
Arjan van de Ven
next prev parent reply other threads:[~2001-05-31 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-31 17:24 Configure.help is complete Eric S. Raymond
2001-05-31 20:13 ` 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 [this message]
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=3B16A01C.ED5C6CCB@redhat.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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