From: Ken Moffat <ken@kenmoffat.uklinux.net>
To: John Bradford <john@grabjohn.com>
Cc: vda@port.imtp.ilyichevsk.odessa.ua,
Chuck Ebbert <76306.1226@compuserve.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Lack of documentation (Was: Re: kernel support for non-English user messages)
Date: Mon, 14 Apr 2003 12:36:14 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.21.0304141226470.4376-100000@ppg_penguin> (raw)
In-Reply-To: <200304141050.h3EAoVKc000205@81-2-122-30.bradfords.org.uk>
On Mon, 14 Apr 2003, John Bradford wrote:
> > > > > /Documentation is *awful*.
>
> > > > You know where to submit contributions
>
> > > If I could *write* the documentation, I wouldn't need it,
> > > now would I? Maybe that's the problem...
>
> > If nobody would write the docs, nobody would read them ;)
>
> Compare:
>
> http://www.gnu.org/software/hurd/hacking-guide/hhg.html
> http://www.gnu.org/software/hurd/users-guide/using_gnuhurd.html
>
> with /Documentation
>
> I think we can do better. I have made several offers to compile
> documentation that is forwarded to me in to a more user-friendly
> format, but few people seem interested.
>
> John.
John, the problem is that documentation either lives within the code,
where it has a small chance of being kept up to date, or it lives
separately and hasn't a cat in hell's chance of staying accurate. Add
in Linus's apparent lack of interest in documentation, and creating an
extra file is just a waste of time, which is a pity.
I like the idea of better documentation, but I don't think we've
started to address the 'what' and 'who-for' questions yet.
(and if anybody wants to respond to me, don't expect prompt answers,
I'll be away from tomorrow until Thursday :)
Ken
--
Out of the darkness a voice spake unto me, saying "smile, things could be
worse". So I smiled, and lo, things became worse.
next prev parent reply other threads:[~2003-04-14 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 20:31 kernel support for non-English user messages Chuck Ebbert
2003-04-14 9:07 ` Denis Vlasenko
2003-04-14 10:50 ` Lack of documentation (Was: Re: kernel support for non-English user messages) John Bradford
2003-04-14 11:36 ` Ken Moffat [this message]
2003-04-14 12:34 ` Denis Vlasenko
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=Pine.LNX.4.21.0304141226470.4376-100000@ppg_penguin \
--to=ken@kenmoffat.uklinux.net \
--cc=76306.1226@compuserve.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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;
as well as URLs for NNTP newsgroup(s).