From: Jim Nelson <james4765@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: Documentation - what work is being done?
Date: Sun, 17 Oct 2004 15:44:41 -0400 [thread overview]
Message-ID: <4172CBA9.5070009@verizon.net> (raw)
Is there any effort being made to update the stuff in the Documentation
directory? Most of the files in there are massively out of date. I'd
like to work on it - but I didn't see an entry for documentation in the
MAINTAINERS file. I googled around for mailing lists for kernel
documentation, but the two I found have been dead for some time.
I think the whole directory needs an overhaul, but there's a lot of
people's work in there (and I'd hate having my work torn to pieces by a
rank amatuer), and I'd like some feedback on where to start, what to
leave alone, what's there for historical interest, and what is
critically needed.
next reply other threads:[~2004-10-17 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 19:44 Jim Nelson [this message]
2004-10-20 10:48 ` Documentation - what work is being done? Adrian Bunk
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=4172CBA9.5070009@verizon.net \
--to=james4765@verizon.net \
--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;
as well as URLs for NNTP newsgroup(s).