All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Jim Nelson <james4765@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Documentation - what work is being done?
Date: Wed, 20 Oct 2004 12:48:21 +0200	[thread overview]
Message-ID: <20041020104821.GA23318@stusta.de> (raw)
In-Reply-To: <4172CBA9.5070009@verizon.net>

On Sun, Oct 17, 2004 at 03:44:41PM -0400, Jim Nelson wrote:

> 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.

Hi Jim,

some documentaion is well maintained while other documentation is no 
longer maintained. If it's maintained, the maintainer of the 
corresponding code is also responsible for the documentation.

If you have a plan how to restructure the documentation mail it to 
linux-kernel and you'll hear the opinion of other people.

Everything else has to be done on a file-per-file basis and usually 
requires a knowledge of the topic a documentation file covers.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2004-10-20 11:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-17 19:44 Documentation - what work is being done? Jim Nelson
2004-10-20 10:48 ` Adrian Bunk [this message]

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=20041020104821.GA23318@stusta.de \
    --to=bunk@stusta.de \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.