From: Randy Dunlap <rdunlap@xenotime.net>
To: lkml <linux-kernel@vger.kernel.org>, linux-doc@vger.kernel.org
Cc: corbet@lwn.net, mtk.manpages@gmail.com, alan@lxorguk.ukuu.org.uk
Subject: [RFC] Documentation tree sub-directories reorg.
Date: Tue, 04 Nov 2008 14:50:36 -0800 [thread overview]
Message-ID: <4910D1BC.9060100@xenotime.net> (raw)
Hi,
I would like to use a few more sub-directories in the Documentation/ tree to
try to help clean it up some. E.g., move some drivers/block/ doc files to
Documentation/blockdev/ and move some serial/tty/chardev doc files to
Documentation/serial/ (or serial-tty/ or chardev/ or <suggestions>).
A [git] diff for blockdev/ and serial/ looks like:
Documentation/00-INDEX | 38 +-------------------------
Documentation/blockdev/00-INDEX | 16 +++++++++++
Documentation/{ => blockdev}/README.DAC960 | 0
Documentation/{ => blockdev}/cciss.txt | 0
Documentation/{ => blockdev}/cpqarray.txt | 0
Documentation/{ => blockdev}/floppy.txt | 0
Documentation/{ => blockdev}/nbd.txt | 0
Documentation/{ => blockdev}/paride.txt | 0
Documentation/{ => blockdev}/ramdisk.txt | 0
Documentation/serial/00-INDEX | 24 +++++++++++++++++
Documentation/{ => serial}/README.cycladesZ | 0
Documentation/{ => serial}/computone.txt | 0
Documentation/{ => serial}/digiepca.txt | 0
Documentation/{ => serial}/hayes-esp.txt | 0
Documentation/{ => serial}/moxa-smartio | 0
Documentation/{ => serial}/riscom8.txt | 0
Documentation/{ => serial}/rocket.txt | 0
Documentation/{ => serial}/specialix.txt | 0
Documentation/{ => serial}/stallion.txt | 0
Documentation/{ => serial}/sx.txt | 0
Documentation/{ => serial}/tty.txt | 0
21 files changed, 42 insertions(+), 36 deletions(-)
create mode 100644 Documentation/blockdev/00-INDEX
rename Documentation/{ => blockdev}/README.DAC960 (100%)
rename Documentation/{ => blockdev}/cciss.txt (100%)
rename Documentation/{ => blockdev}/cpqarray.txt (100%)
rename Documentation/{ => blockdev}/floppy.txt (100%)
rename Documentation/{ => blockdev}/nbd.txt (100%)
rename Documentation/{ => blockdev}/paride.txt (100%)
rename Documentation/{ => blockdev}/ramdisk.txt (100%)
create mode 100644 Documentation/serial/00-INDEX
rename Documentation/{ => serial}/README.cycladesZ (100%)
rename Documentation/{ => serial}/computone.txt (100%)
rename Documentation/{ => serial}/digiepca.txt (100%)
rename Documentation/{ => serial}/hayes-esp.txt (100%)
rename Documentation/{ => serial}/moxa-smartio (100%)
rename Documentation/{ => serial}/riscom8.txt (100%)
rename Documentation/{ => serial}/rocket.txt (100%)
rename Documentation/{ => serial}/specialix.txt (100%)
rename Documentation/{ => serial}/stallion.txt (100%)
rename Documentation/{ => serial}/sx.txt (100%)
rename Documentation/{ => serial}/tty.txt (100%)
Comments/thoughts?
Thanks,
~Randy
[The git tree is not currently on a shared system.]
next reply other threads:[~2008-11-04 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 22:50 Randy Dunlap [this message]
2008-11-04 23:23 ` [RFC] Documentation tree sub-directories reorg Jonathan Corbet
2008-11-07 19:17 ` Rob Landley
2008-11-07 19:13 ` Rob Landley
2008-11-09 20:13 ` J. Bruce Fields
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=4910D1BC.9060100@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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