commit d348ac0d914cccc1a58f4e5daab35f170633cade
Author: Halil Pasic <pasic@linux.vnet.ibm.com>
Date: Tue Feb 13 13:44:08 2018 +0100
introduction: simplify the designation of legacy
The sentence designating the documents defining what later
became known as the legacy virtio interface had the most
important piece of information placed in parenthesis.
Let's reword this sentence so we avoid using an ambiguous designation
based on a relative anchor (i.e. 'earlier drafts of this specification')
and just use the absolute anchor (version 1.0).
VIRTIO-164
Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
diff --git a/introduction.tex b/introduction.tex
index a4ac01d..c5ccd89 100644
— a/introduction.tex
+++ b/introduction.tex
@@ -78,8 +78,8 @@ The key words ``MUST'', ``MUST NOT'', ``REQUIRED'', ``SHALL'', ``SHALL NOT'', ``
\subsection
{Legacy Interface: Terminology}
\label
{intro:Legacy
Interface: Terminology}
-Earlier drafts of this specification (i.e. revisions before 1.0,
-see e.g. \hyperref[intro:Virtio PCI Draft]
{[Virtio PCI Draft]})
+Specification drafts preceding version 1.0 of this specification
+(e.g. see \hyperref
[intro:Virtio PCI Draft]{[Virtio PCI Draft]}
)
defined a similar, but different
interface between the driver and the device.
Since these are widely deployed, this specification