From: Jim Nelson <james4765@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: [RFC] Structural changes for Documentation directory
Date: Wed, 20 Oct 2004 16:51:47 -0400 [thread overview]
Message-ID: <4176CFE3.2030306@verizon.net> (raw)
I propose changing the structure of the Documentation directory to
reflect the structure of the kernel sources itself.
How I see it working is: (Excuse the ASCII-art)
Documentation/
|
|____ arch/
| |
| |____ i386/
| |
| |____ s390/
| |
| |____ (etc.)
|
|____ drivers/
| |
| |____ cdrom/
| |
| |____ serial/
| |
| |____ (etc.)
|
|____ net/
| |
| |____ sunrpc/
| |
| |____ atm/
| |
| |____ (etc.)
|
|____ kernel/
|
|____ mm/
With the files that have no real home in the source (SubmittingPatches,
CodingStyle, kernel-docs.txt, etc) to remain in the main directory.
Perhaps it would be best to put the new tree in place and have the
individual maintainers relocate their documentation to the new
structure? This would also be a good way to find out what files are
orphaned, and are in need of update or removal.
Comments? Additions? Warnings?
next reply other threads:[~2004-10-20 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 20:51 Jim Nelson [this message]
2004-10-20 22:23 ` [RFC] Structural changes for Documentation directory Nigel Cunningham
2004-10-20 22:44 ` Måns Rullgård
2004-10-20 22:30 ` Andrew Morton
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=4176CFE3.2030306@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