From: Pekka Enberg <penberg@gmail.com>
To: Stephane Wirtel <stephane.wirtel@belgacom.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Documentation] Use doxygen or another tool to generate a documentation ?
Date: Sat, 20 Aug 2005 00:46:22 +0300 [thread overview]
Message-ID: <84144f02050819144660238be4@mail.gmail.com> (raw)
In-Reply-To: <20050819213447.GA9538@localhost.localdomain>
On 8/20/05, Stephane Wirtel <stephane.wirtel@belgacom.net> wrote:
> I don't know if there is a project based on Doxygen to make
> (or generate) a documentation of the kernel.
>
> Do you think that will be interesting to make a such document ?
The kernel already has it's own API documentation generator called
kerneldoc. See the file Documentation/kernel-doc-nano-HOWTO.txt for
details.
Pekka
next prev parent reply other threads:[~2005-08-19 21:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 21:34 [Documentation] Use doxygen or another tool to generate a documentation ? Stephane Wirtel
2005-08-19 21:46 ` Pekka Enberg [this message]
2005-08-19 23:23 ` Stephane Wirtel
2005-08-20 7:41 ` Sam Ravnborg
2005-08-20 9:19 ` Stephane Wirtel
2005-08-20 17:37 ` Sam Ravnborg
2005-08-21 12:28 ` Stephane Wirtel
2005-08-21 15:12 ` Martin Waitz
2005-08-21 18:32 ` Stephane Wirtel
2005-08-22 7:45 ` Martin Waitz
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=84144f02050819144660238be4@mail.gmail.com \
--to=penberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stephane.wirtel@belgacom.net \
/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