From: Andries.Brouwer@cwi.nl
To: ramsy@linux.or.jp, torvalds@transmeta.com
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: Configure.help i18n system
Date: Thu, 7 Jun 2001 23:46:20 +0200 (MET DST) [thread overview]
Message-ID: <UTC200106072146.XAA217951.aeb@vlet.cwi.nl> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
> I wonder if the Configure.help text should not possibly be even _more_
> distributed than just splitting it up into different files. It might very
> well be acceptable to actually distribute it over the net (and have just
> a mapping of config options into www-addresses or something).
I think this is a bad idea.
(i) The kernel has high visibility, and work on the kernel
[even if only on the Documentation subdirectory] has high "prestige".
As a consequence, parts of the kernel tree are kept much better
up-to-date than documentation found elsewhere.
(I have been trying for years to find people willing to do something
to the very outdated ioctl_list.2 or proc.5 or bootparam.7.)
When distributed, very quickly Configure.help would be outdated,
and of very uneven format and quality.
(ii) So far, building a kernel involved getting a single tarball.
If the help for over a thousand configuration options is found
a hundred different places on the net, of which five are currently
unreachable, things get really cumbersome.
The current system is not so bad.
Andries
next reply other threads:[~2001-06-07 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-07 21:46 Andries.Brouwer [this message]
2001-06-08 9:12 ` Francois Romieu
[not found] <20010607165007.A299.RAMSY@linux.or.jp>
2001-06-07 21:01 ` Linus Torvalds
2001-06-07 21:23 ` Horst von Brand
2001-06-07 21:44 ` Richard Gooch
2001-06-08 1:21 ` GOTO Masanori
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=UTC200106072146.XAA217951.aeb@vlet.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ramsy@linux.or.jp \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®