From: Jarek Poplawski <jarkao2@o2.pl>
To: Glenn Enright <elinar@ihug.co.nz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] DocBook with .txt or .html versions?
Date: Thu, 19 Oct 2006 12:09:33 +0200 [thread overview]
Message-ID: <20061019100932.GC3296@ff.dom.local> (raw)
In-Reply-To: <200610192214.23618.elinar@ihug.co.nz>
On Thu, Oct 19, 2006 at 10:14:23PM +1300, Glenn Enright wrote:
> On Thursday 19 October 2006 21:58, Jarek Poplawski wrote:
> > On Thu, Oct 19, 2006 at 09:29:45PM +1300, Glenn Enright wrote:
> > > Doesnt slackware supply a prebuilt package of the kernel docs in
> > > various formats for just this purpose? From what I can recall,
> > > redhat and ubuntu both do this.
> >
> > Maybe does. But do you believe there is anybody reading
> > this list who uses only distro's prebuilt kernel versions?
> >
> > Jarek P.
>
> You implied that you were trying to build on a limited resource machine,
> and I offered this as an alternative. If you really needed the *very
> latest* docs then it would probably be a newish testing platform and
> not your main machine, so you could get them of that instead? Anyway
> just my 2c.
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.
Thanks for your 2c (they are rarity here!),
Jarek P.
next prev parent reply other threads:[~2006-10-19 10:04 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 [this message]
2006-10-19 10:29 ` Glenn Enright
2006-10-19 11:16 ` Jarek Poplawski
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=20061019100932.GC3296@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=elinar@ihug.co.nz \
--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