From: "J. Bruce Fields" <bfields@fieldses.org>
To: Rob Landley <rob@landley.net>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
lkml <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, corbet@lwn.net,
mtk.manpages@gmail.com, alan@lxorguk.ukuu.org.uk
Subject: Re: [RFC] Documentation tree sub-directories reorg.
Date: Sun, 9 Nov 2008 15:13:57 -0500 [thread overview]
Message-ID: <20081109201357.GB27376@fieldses.org> (raw)
In-Reply-To: <200811071313.50384.rob@landley.net>
On Fri, Nov 07, 2008 at 01:13:49PM -0600, Rob Landley wrote:
> On Tuesday 04 November 2008 16:50:36 Randy Dunlap wrote:
> > 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:
> ...
> > Comments/thoughts?
>
> That's a good start. It would also be nice to create an "arch" subdirectory
> to move the arm, m68k, mips, blackfin, parisc, powerpc, s390, sparc, ia64,
> uml, and x86 directories into. (Plus sgi-*, voyager.txt, zorro.txt...)
I started doing some of this here:
git://linux-nfs.org/~bfields/linux.git for-joncorbet
but didn't get very far. (But in the remote chance there's something
useful there, feel free to cannibalize it.)
--b.
prev parent reply other threads:[~2008-11-09 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 22:50 [RFC] Documentation tree sub-directories reorg Randy Dunlap
2008-11-04 23:23 ` Jonathan Corbet
2008-11-07 19:17 ` Rob Landley
2008-11-07 19:13 ` Rob Landley
2008-11-09 20:13 ` J. Bruce Fields [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=20081109201357.GB27376@fieldses.org \
--to=bfields@fieldses.org \
--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 \
--cc=rdunlap@xenotime.net \
--cc=rob@landley.net \
/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.