From: "Michael S. Tsirkin" <mst@redhat.com>
To: Chet Ensign <chet.ensign@oasis-open.org>
Cc: Patrick Durusau <patrick@durusau.net>,
virtio-comment@lists.oasis-open.org,
OASIS TAB <tab@lists.oasis-open.org>
Subject: [virtio-comment] Re: [tab] Re: [virtio-comment] TAB comments on Virtual I/O Device (VIRTIO) Version 1.1
Date: Wed, 27 Feb 2019 10:46:22 -0500 [thread overview]
Message-ID: <20190227104327-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAAwgnnOtb40f+e9DkwLKkLRp3VhsRyCJ2oqzosWykjhx-X9yZA@mail.gmail.com>
See VIRTIO-175 (link died, and this isn't the first time for IEEE)
as well as VIRTIO-173 (a bunch of links which now redirect, but
we have no idea whether the old or the new link is
more likely to stay live for longer).
On Wed, Feb 27, 2019 at 10:42:12AM -0500, Chet Ensign wrote:
> Michael, where are the links you are referring to? Can you point me to some
> examples?
>
> On Wed, Feb 27, 2019 at 10:14 AM Michael S. Tsirkin <mst@redhat.com> wrote:
>
> Chet, I have a question:
> lots of links to other specifications moved around since virtio 1.0.
> Some have a redirect. Some are just silently broken. Sure we can keep
> chasing them around but I wonder about the utility of this.
>
> OASIS is in fact unusual in that it tries hard to keep old links alive.
>
> Is there an issue wrt OASIS bylaws to link to a wikipedia page instead?
> Hard to make any guarantees anyway, but at least for now there are
> people that watch this space and keep updating the links there. For
> example:
>
> https://en.wikipedia.org/wiki/IEEE_802
>
> instead of the (now dead)
> http://standards.ieee.org/about/get/802/802.html
>
> Thanks!
>
> --
> MST
>
>
>
> --
>
> /chet
> ----------------
> Chet Ensign
> Chief Technical Community Steward
> OASIS: Advancing open standards for the information society
> http://www.oasis-open.org
>
> Primary: +1 973-996-2298
> Mobile: +1 201-341-1393
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2019-02-27 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 22:36 [virtio-comment] TAB comments on Virtual I/O Device (VIRTIO) Version 1.1 Patrick Durusau
2019-02-26 20:58 ` Michael S. Tsirkin
2019-02-26 21:29 ` [virtio-comment] Re: [tab] " Chet Ensign
2019-02-27 14:10 ` Michael S. Tsirkin
2019-02-27 14:20 ` Chet Ensign
2019-02-27 14:31 ` Patrick Durusau
2019-02-27 14:35 ` Chet Ensign
2019-02-27 15:14 ` Michael S. Tsirkin
2019-02-27 15:42 ` Chet Ensign
2019-02-27 15:46 ` Michael S. Tsirkin [this message]
2019-02-27 15:50 ` Michael S. Tsirkin
2019-02-27 20:49 ` Patrick Durusau
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=20190227104327-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=chet.ensign@oasis-open.org \
--cc=patrick@durusau.net \
--cc=tab@lists.oasis-open.org \
--cc=virtio-comment@lists.oasis-open.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 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.