From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Michael Opdenacker <michael.opdenacker@free-electrons.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: replace broken specification URL
Date: Sat, 02 Jul 2016 07:49:31 -0700 [thread overview]
Message-ID: <1467470971.2400.7.camel@HansenPartnership.com> (raw)
In-Reply-To: <1467442596-31310-1-git-send-email-michael.opdenacker@free-electrons.com>
On Sat, 2016-07-02 at 08:56 +0200, Michael Opdenacker wrote:
> The t10.org website containing SCSI-2 draft specifications now
> requires to be from a member company to access the documents.
>
> This replaces the now broken link with another public resource
> where the specifications can be found.
Just because T10 implemented a pay wall for standards, doesn't mean
they're not still the definitive source.
Adding a note about where you can get free versions is a useful
service, please do, but we have to keep the official links. To be
honest the Duisberg site doesn't seem useful because it only has the
CAM standard.
The Wayback machine is more useful because it keeps a copy of the site
(with the attached standards) just before the paywall went up:
https://web.archive.org/web/20080828112749/http://t10.org/drafts.htm
But that only really has pre 2008 standards.
James
next prev parent reply other threads:[~2016-07-02 14:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 6:56 [PATCH] scsi: replace broken specification URL Michael Opdenacker
2016-07-02 14:49 ` James Bottomley [this message]
2016-09-09 8:16 ` Michael Opdenacker
2016-09-09 22:53 ` Tyrel Datwyler
2016-09-14 17:00 ` Martin K. Petersen
2016-09-15 12:33 ` Michael Opdenacker
2016-09-15 13:03 ` Michael Opdenacker
2016-09-15 14:06 ` Martin K. Petersen
2016-09-16 1:00 ` Laurence Oberman
2016-09-16 0:57 ` Laurence Oberman
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=1467470971.2400.7.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michael.opdenacker@free-electrons.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 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.