From: Douglas Gilbert <dougg@torque.net>
To: linux-kernel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org,
Rolf Eike Beer <eike@bilbo.math.uni-mannheim.de>
Subject: Re: [RFC] Clean up scsi documentation
Date: Sun, 10 Nov 2002 09:49:43 +1100 [thread overview]
Message-ID: <3DCD9107.3020103@torque.net> (raw)
Eike Beer <eike@bilbo.math.uni-mannheim.de> wrote:
> currently the documentation for scsi is not completely located
> where it should IMHO be: in Documentation/
>
> There are a few files in Documentation and much more files in
> drivers/scsi/ .
> I think this should be fixed. Any thougts?
>
> My way would be:
>
> 1) create a directory Documentation/scsi/
> 2) move everything to this location
> 3) rename some of the docs (currently the names look
> like "README.drivername"
> but "drivername.txt" is more common in Documentation/*)
> 4) fix up the references
> 5) add a 00-INDEX file to Documentation/scsi
<snip/>
Yes, this would be a positive step and has been proposed by
others on the linux-scsi list. It may be a bit late for the
2.4 series but the time would be right for the 2.5 series.
James Bottomley <James.Bottomley@steeleye.com> and Doug Ledford
<dledford@redhat.com> are maintaining BK repositories for the
scsi subsystem in the 2.5 series. If you could submit your
patches to them, then they will find their way to Linus
in an orderly fashion.
Doug Gilbert
next reply other threads:[~2002-11-09 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-09 22:49 Douglas Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-09 22:01 [RFC] Clean up scsi documentation Rolf Eike Beer
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=3DCD9107.3020103@torque.net \
--to=dougg@torque.net \
--cc=eike@bilbo.math.uni-mannheim.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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