From: Oleg Verych <olecom@flower.upol.cz>
To: Sam Ravnborg <sam@ravnborg.org>,
Stephen Hemminger <shemminger@linux-foundation.org>
Cc: <hjk@linutronix.de>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: Documentation files in html format?
Date: Sat, 1 Sep 2007 20:39:14 +0200 [thread overview]
Message-ID: <E1IRXsI-0008Qt-CF@flower> (raw)
In-Reply-To: <20070810074047.GC31307@uranus.ravnborg.org>
* Date: Fri, 10 Aug 2007 09:40:47 +0200
* Sam Ravnborg:
>
> Documentation should be easy to access and readable in the source format.
> For this purpose asciidoc seems to do a good job.
>
> It is btw. discussed at git ML if they should shift due to toolset being
> slow but that happens to be the docbook utilities. asciidoc seems to be fast enough.
> And it can produce both HTML and docbook so seems to cover all cases.
just plain text
another option: txt2tags && sed
For me anything else, like man, info, (xml, html)+css, is a brain
damage. If it's fine for you -- it's your wasted time and mood.
(yet another big useless thread on useless OT, how sad).
____
next prev parent reply other threads:[~2007-09-01 18:42 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
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 [this message]
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=E1IRXsI-0008Qt-CF@flower \
--to=olecom@flower.upol.cz \
--cc=andi@firstfloor.org \
--cc=hjk@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=shemminger@linux-foundation.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 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.