From: Rob Landley <rob@landley.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
lkml <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, mtk.manpages@gmail.com,
alan@lxorguk.ukuu.org.uk
Subject: Re: [RFC] Documentation tree sub-directories reorg.
Date: Fri, 7 Nov 2008 13:17:17 -0600 [thread overview]
Message-ID: <200811071317.19159.rob@landley.net> (raw)
In-Reply-To: <20081104162345.38729b20@bike.lwn.net>
On Tuesday 04 November 2008 17:23:45 Jonathan Corbet wrote:
> On Tue, 04 Nov 2008 14:50:36 -0800
>
> Randy Dunlap <rdunlap@xenotime.net> wrote:
> > 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/
>
> This all makes fine sense to me, but I do wonder if we shouldn't also
> create an "obsolete" subdirectory and put some of those files there?
> For example, paride.txt starts off this way:
>
> Owing to the simplicity and near universality of the parallel port
> interface to personal computers, many external devices such as
> portable hard-disk, CD-ROM, LS-120 and tape drives use the parallel
> port to connect to their host computer.
>
> Said ports are not quite as universal as they once were.
Yeah, but the robotics guys guys love 'em as a really easy way to get
controllable pinouts from PC hardware. :)
No objection to the idea of a place to put obsolete docs,
although "deprecated" might be a better name and it seems like it relates to
feature-removal-schedule.txt somehow...
Rob
next prev parent reply other threads:[~2008-11-07 19:15 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 [this message]
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=200811071317.19159.rob@landley.net \
--to=rob@landley.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 \
--cc=rdunlap@xenotime.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.