From: Rene Herman <rene.herman@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "Stefan Richter" <stefanr@s5r6.in-berlin.de>,
"Andi Kleen" <andi@firstfloor.org>,
"Hans-Jürgen Koch" <hjk@linutronix.de>,
"Stephen Hemminger" <shemminger@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: Documentation files in html format?
Date: Sat, 11 Aug 2007 01:27:20 +0200 [thread overview]
Message-ID: <46BCF458.7010300@gmail.com> (raw)
In-Reply-To: <20070810201235.GA4133@uranus.ravnborg.org>
On 08/10/2007 10:12 PM, Sam Ravnborg wrote:
>> What primary requirements does in-tree Linux kernel documentation have
>> to fulfill in general?
>
> Skipping the obvious ones such as correct, up-to-date etc.
> o Readable as-is
> o Grepable
> o buildable as structured documents or almost like a single book
> o Easy to replicate structure
> o Maintainable in any decent text-editor (emacs, vim, whatever)
Easy to put online?
> Asciidoc is quite close to plaintext and it looks to me that the
> formatting possibilities are quite good.
>
> I spend an hour experimenting a little with
> Documentation/kbuild/makefiles.txt.
>
> Diff below shows quite a lot of changes but for the most
> this is removal of the indent tab.
> Most likely I could have tweaked asciidoc to accept this
> but wanted to use default config.
>
> The resulting html page can be seen here:
> http://www.ravnborg.org/kbuild/makefiles.html
FWIW, this looks very good to me...
Rene.
next prev parent reply other threads:[~2007-08-10 23:31 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 10:31 Documentation files in html format? Stephen Hemminger
2007-08-09 10:49 ` Jan Engelhardt
2007-08-09 13:08 ` Hans-Jürgen Koch
2007-08-09 13:22 ` Stephen Hemminger
2007-08-09 15:26 ` Andi Kleen
2007-08-09 14:37 ` Rene Herman
2007-08-09 15:15 ` Jarek Poplawski
2007-08-09 19:10 ` Francois Romieu
2007-08-09 19:30 ` Andi Kleen
2007-08-09 22:27 ` Francois Romieu
2007-08-10 0:15 ` Rene Herman
2007-08-10 7:40 ` Sam Ravnborg
2007-08-10 13:52 ` Stefan Richter
2007-08-10 20:12 ` Sam Ravnborg
2007-08-10 23:27 ` Rene Herman [this message]
2007-08-11 6:31 ` Stefan Richter
2007-08-11 19:12 ` Rene Herman
2007-08-11 15:53 ` Jan Engelhardt
2007-08-11 22:55 ` Randy Dunlap
2007-08-12 3:11 ` Randy Dunlap
2007-08-12 3:27 ` Sam Ravnborg
2007-09-01 18:39 ` Oleg Verych
2007-08-09 17:56 ` Bob Copeland
2007-08-09 19:14 ` Stefan Richter
2007-08-09 19:58 ` Brennan Ashton
2007-08-09 20:03 ` Jesper Juhl
2007-08-09 20:08 ` Jan Engelhardt
2007-08-10 20:17 ` Willy Tarreau
2007-08-10 20:40 ` J. Bruce Fields
2007-08-10 20:51 ` Willy Tarreau
2007-08-10 23:08 ` Sam Ravnborg
2007-08-11 5:33 ` Willy Tarreau
2007-08-11 14:19 ` J. Bruce Fields
2007-08-11 14:17 ` Willy Tarreau
2007-08-11 23:00 ` Randy Dunlap
2007-08-12 3:12 ` Randy Dunlap
2007-08-12 13:10 ` Stefan Richter
2007-08-12 15:43 ` Sam Ravnborg
2007-08-12 18:25 ` Stefan Richter
2007-08-11 23:12 ` Randy Dunlap
2007-08-12 3:12 ` Randy Dunlap
[not found] <8QdB3-87O-7@gated-at.bofh.it>
[not found] ` <8QdUr-5j-11@gated-at.bofh.it>
2007-08-09 12:34 ` Bodo Eggert
2007-08-09 12:41 ` Jan Engelhardt
2007-08-09 13:29 ` Bodo Eggert
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=46BCF458.7010300@gmail.com \
--to=rene.herman@gmail.com \
--cc=andi@firstfloor.org \
--cc=hjk@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=shemminger@linux-foundation.org \
--cc=stefanr@s5r6.in-berlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.