mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: 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: Tue, 4 Nov 2008 16:23:45 -0700	[thread overview]
Message-ID: <20081104162345.38729b20@bike.lwn.net> (raw)
In-Reply-To: <4910D1BC.9060100@xenotime.net>

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.  The document also
points to a nonexistent web page and a dead mailing list.  It's hard to
imagine that it's actually doing anybody any good at all.  Even if somebody
out there is still using the paride drivers (can there possibly be?), they
aren't likely to be getting much help here.

jon

  reply	other threads:[~2008-11-04 23:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 22:50 Randy Dunlap
2008-11-04 23:23 ` Jonathan Corbet [this message]
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=20081104162345.38729b20@bike.lwn.net \
    --to=corbet@lwn.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®