From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>,
mst@redhat.com, virtio-dev@lists.oasis-open.org
Cc: virtio-comment@lists.oasis-open.org, shahafs@nvidia.com,
Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] Re: [virtio-comment] [PATCH] introduction: Add missing helping verb
Date: Wed, 12 Apr 2023 10:47:09 +0200 [thread overview]
Message-ID: <87wn2hjxma.fsf@redhat.com> (raw)
In-Reply-To: <20230411192554.751994-1-parav@nvidia.com>
On Tue, Apr 11 2023, Parav Pandit <parav@nvidia.com> wrote:
> The terminology of Transitional device and driver is missing the helping
> verb 'is' similar to other terminologies.
>
> Hence, add them to complete the sentence.
>
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> ---
> introduction.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/introduction.tex b/introduction.tex
> index 287c5fc..e8b34e3 100644
> --- a/introduction.tex
> +++ b/introduction.tex
> @@ -145,14 +145,14 @@ \subsection{Legacy Interface: Terminology}\label{intro:Legacy
>
> \begin{description}
> \item[Transitional Device]
> - a device supporting both drivers conforming to this
> + is a device supporting both drivers conforming to this
> specification, and allowing legacy drivers.
> \end{description}
>
> Similarly, a driver MAY implement:
> \begin{description}
> \item[Transitional Driver]
> - a driver supporting both devices conforming to this
> + is a driver supporting both devices conforming to this
> specification, and legacy devices.
> \end{description}
I'd rather not add the "is" (and drop the trailing ".", as this is not
supposed to be a sentence), as this would read awkwardly. I think it is
intended to be:
<xyz> MAY implement:
<list of things>
which does not really ask for a sentence.
Same thing applies to the section right above, where it talks about
legacy support; I'd drop the "is" there instead.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
prev parent reply other threads:[~2023-04-12 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 19:25 [virtio-dev] [PATCH] introduction: Add missing helping verb Parav Pandit
2023-04-12 8:47 ` Cornelia Huck [this message]
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=87wn2hjxma.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox