From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation updates
Date: Wed, 26 Jan 2005 11:02:06 +0000 [thread overview]
Message-ID: <20050126110206.GA8306@infradead.org> (raw)
In-Reply-To: <20050126105621.GW3069@admingilde.org>
On Wed, Jan 26, 2005 at 11:56:21AM +0100, Martin Waitz wrote:
> hoi :)
>
> I have created some updates to the Linux documentation.
>
> This includes two important fixes that allow to generate DocBook
> documenation from kernel-doc comments again and some low-priority
> updates to the kernel-doc comments itself.
>
> All patches are available in my BK repository, it only contains
> documentation updates, no code changes.
> (The fixes have been reported here before but have not been merged yet.)
Cool! Btw, anybody's got an idea how to speedup generating the documentation
from the DocBook templates? There surely must be some faster parsers, it's
currently taking up the majority of the time used to build kernel-source
packages on Debian.
next prev parent reply other threads:[~2005-01-26 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 10:56 [PATCH] Documentation updates Martin Waitz
2005-01-26 11:02 ` Christoph Hellwig [this message]
2005-01-26 15:45 ` Randy.Dunlap
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=20050126110206.GA8306@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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