From: Charles Samuels <charles@kde.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel Documentation
Date: Tue, 17 Jul 2001 14:25:03 -0700 [thread overview]
Message-ID: <200107172125.OAA20013@altair.dhs.org> (raw)
In-Reply-To: <200107172102.OAA19756@altair.dhs.org> <20010717171843.C21825@mueller.datastacks.com>
In-Reply-To: <20010717171843.C21825@mueller.datastacks.com>
BTW:
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?
>
> 2: the secondary issue of documenting best practices in the
> kernel is a different matter altogether. I, myself, have started
> a project to do this. I'm sorta scared of letting people know
> about it at this point, but I feel it is necessary.
>
> the entry point is:
> http://bama.ua.edu/~dunn001/journeyman/
404. Not sure what this is anyway :)
>
> I /am/ looking for help, but it is very early. I am NOT looking
> for exposure, so dont even bother looking if you dont want to write
> docs; there isnt anything there for you.
next prev parent reply other threads:[~2001-07-17 21:25 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 [this message]
2001-07-17 21:31 ` Charles Samuels
2001-07-18 2:19 ` John Levon
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=200107172125.OAA20013@altair.dhs.org \
--to=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