From: John Levon <moz@compsoc.man.ac.uk>
To: linux-kernel@vger.kernel.org
Cc: charles@kde.org
Subject: Re: Kernel Documentation
Date: Wed, 18 Jul 2001 03:19:18 +0100 [thread overview]
Message-ID: <20010718031917.A8164@compsoc.man.ac.uk> (raw)
In-Reply-To: <200107172102.OAA19756@altair.dhs.org> <20010717171843.C21825@mueller.datastacks.com> <200107172125.OAA20013@altair.dhs.org>
In-Reply-To: <200107172125.OAA20013@altair.dhs.org>
On Tue, Jul 17, 2001 at 02:25:03PM -0700, Charles Samuels wrote:
> On Tuesday 17 July 2001 02:18 pm, you wrote:
> > ++ 17/07/01 14:02 -0700 - Charles Samuels:
> > 2 things:
> >
> > 1: there is a project in the kernel to establish API references.
> > you should not duplicate this work, but should add to it.
> > Reason: There is no way you can get or stay ahead.
>
> make htmldoc ? I don't have docbook, and don't want to have to install it,
> well, unless I know that it'l get me what I want. Does it create an actual
> API reference?
yes. you can read a recent version at http://kernelnewbies.org/documents/kdoc/
Everyone would much prefer it if you pitched in with this instead I think...
one simple advantage is the docs are inline so have a slightly higher chance
of staying up to date.
regards
john
--
"Voodoo Programming: Things programmers do that they know shouldn't work but
they try anyway, and which sometimes actually work, such as recompiling
everything."
- Karl Lehenbauer
next prev parent reply other threads:[~2001-07-18 2:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 21:02 Kernel Documentation Charles Samuels
2001-07-17 21:18 ` Crutcher Dunnavant
2001-07-17 21:25 ` Charles Samuels
2001-07-17 21:31 ` Charles Samuels
2001-07-18 2:19 ` John Levon [this message]
2001-07-18 9:06 ` Tim Jansen
2001-07-18 10:18 ` Tim Waugh
2001-07-17 21:28 ` Ignacio Vazquez-Abrams
2001-07-17 21:32 ` Crutcher Dunnavant
2001-07-17 21:28 ` Wichert Akkerman
-- strict thread matches above, loose matches on Subject: below --
2001-07-17 20:24 Charles Samuels
2001-07-17 20:46 ` Ignacio Vazquez-Abrams
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=20010718031917.A8164@compsoc.man.ac.uk \
--to=moz@compsoc.man.ac.uk \
--cc=charles@kde.org \
--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