public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Jim Nelson <james4765@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Structural changes for Documentation directory
Date: Wed, 20 Oct 2004 15:30:58 -0700	[thread overview]
Message-ID: <20041020153058.6de41ed8.akpm@osdl.org> (raw)
In-Reply-To: <4176CFE3.2030306@verizon.net>

Jim Nelson <james4765@verizon.net> wrote:
>
> I propose changing the structure of the Documentation directory to 
> reflect the structure of the kernel sources itself.

That sounds like a bit of overdesign, really.  Take it one step at a time.

Sure, if you're really prepared to do a large-scale overhaul then the first
step is to create a new top-level directory, say
"./non-crappy-Documentation" and then move files over into there as they
are fixed up.  That way we have a good handle on what is done and what
remains.  You can then make decisions about the directory structure
on an incremental basis as you become more familiar with the problem.

> Perhaps it would be best to put the new tree in place and have the 
> individual maintainers relocate their documentation to the new 
> structure?

Maintainers studiously ignore the Documentation directory.  If someone
really wishes to get in there and fix it all up, that person gets to decide
what goes where and that person gets to harrass various other maintainers
when assistance is needed.


  parent reply	other threads:[~2004-10-20 22:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20 20:51 [RFC] Structural changes for Documentation directory Jim Nelson
2004-10-20 22:23 ` Nigel Cunningham
2004-10-20 22:44   ` Måns Rullgård
2004-10-20 22:30 ` Andrew Morton [this message]
2004-10-20 22:51   ` Jim Nelson
2004-10-21  4:20     ` Dave Jones
2004-10-21  4:38       ` Jim Nelson
2004-10-21  5:00         ` Andrew Morton
2004-10-21  5:05           ` Dave Jones
2004-10-21  5:07             ` Andrew Morton
2004-10-21  9:43             ` Jim Nelson

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=20041020153058.6de41ed8.akpm@osdl.org \
    --to=akpm@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox