From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Daniel Phillips <phillips@innominate.de>
Cc: caperry@edolnx.net, linux-kernel@vger.kernel.org,
Ben LaHaise <bcrl@redhat.com>
Subject: Re: Kernel Development Documentation?
Date: Fri, 08 Dec 2000 10:57:56 -0500 [thread overview]
Message-ID: <3A310504.8AB07E6D@mandrakesoft.com> (raw)
In-Reply-To: <E144O3Q-0003vP-00@the-village.bc.nu> <00120816515701.00491@gimli>
Daniel Phillips wrote:
> On Fri, 08 Dec 2000, Alan Cox wrote:
> > For the kernel stuff there is a project to put documentation about functions
> > and what they do inline into the kernel. Its slow progress. Trying to do
> > anything formal and structured isnt going to be productive until the
> > documentation is much much more complete
> Tigran Aivazian has been preparing 'Linux Kernel Internals' which is
> *highly recommended* and 100% free. Why don't you get together with
> him, and Gary Lawrence Murphy (see his monthy kernel wiki nag)?
>
> Personally, I try to do the right thing and submit at least one piece
> of documentation per month to somebody's documenation project but...
> it's not always so easy to free up the required hour or two. This
> month my feeble attempt consisted of nagging Ben LaHaise to submit a
> particularly lucid email he sent me as a code comment.
Lucid e-mails often get stuck into Documentation/*, that's fine.
The preferred is 'make {pdf,ps,html}docs' as yanked from
Documentation/DocBook.
Jeff
--
Jeff Garzik |
Building 1024 | These are not the J's you're lookin' for.
MandrakeSoft | It's an old Jedi mind trick.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-08 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 4:41 Carl Perry
2000-12-08 4:46 ` Jeff V. Merkey
2000-12-08 13:59 ` Alan Cox
2000-12-08 15:17 ` Daniel Phillips
2000-12-08 15:57 ` Jeff Garzik [this message]
2000-12-08 16:13 ` Tigran Aivazian
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=3A310504.8AB07E6D@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=bcrl@redhat.com \
--cc=caperry@edolnx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@innominate.de \
/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
all inboxes | Powered by JetHome®