From: Jarek Poplawski <jarkao2@o2.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] DocBook with .txt or .html versions?
Date: Thu, 19 Oct 2006 13:16:20 +0200 [thread overview]
Message-ID: <20061019111620.GD3296@ff.dom.local> (raw)
In-Reply-To: <200610192329.07361.elinar@ihug.co.nz>
On Thu, Oct 19, 2006 at 11:29:07PM +1300, Glenn Enright wrote:
> On Thursday 19 October 2006 23:09, Jarek Poplawski wrote:
> > I'm sorry if I implied... It is not a problem of limited resources.
> > If I can choose I allways tend to install only necessary software.
> I suppose that certainly helps when chasing bugs.
There are also security reasons.
> Did you have an
> alternative way of building the docs in mind that could be lighter? I
> admit the tree you described does seem a large pull just so you can
> read some text for one source package... even if it is the kernel.
Yes. My preferred alternative way is used by
all the rest of Documentation already.
My other preferred alternative way, used by
many programs like apache, postgresql, mysql,
samba etc. is html, which could be read even
on consoles with lynx or links.
If there is a problem of space let it be
accessible in ftp subdirectory at least.
Cheers,
Jarek P.
next prev parent reply other threads:[~2006-10-19 11:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 11:42 [RFC] DocBook with .txt or .html versions? Jarek Poplawski
2006-10-18 15:41 ` Randy Dunlap
2006-10-19 5:51 ` Jarek Poplawski
[not found] ` <200610192129.46103.elinar@ihug.co.nz>
2006-10-19 8:58 ` Jarek Poplawski
2006-10-19 9:14 ` Glenn Enright
2006-10-19 10:09 ` Jarek Poplawski
2006-10-19 10:29 ` Glenn Enright
2006-10-19 11:16 ` Jarek Poplawski [this message]
2006-10-20 5:30 ` [RFC] DocBook with .txt or .html versions? [KORG] Jarek Poplawski
2006-10-20 5:45 ` Glenn Enright
2006-10-20 7:12 ` Jarek Poplawski
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=20061019111620.GD3296@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=linux-kernel@vger.kernel.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