From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>,
"virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>,
"cohuck@redhat.com" <cohuck@redhat.com>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: Re: [PATCH] device-parts: editorial: Fix metadata type name
Date: Wed, 11 Sep 2024 06:01:44 -0400 [thread overview]
Message-ID: <20240911060140-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <IA0PR12MB8713E6440868B97D63A52396DC9B2@IA0PR12MB8713.namprd12.prod.outlook.com>
On Wed, Sep 11, 2024 at 03:19:45AM +0000, Parav Pandit wrote:
>
>
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Wednesday, September 11, 2024 1:51 AM
>
> [..]
> > > It is already in italics.
> > >
> > > The question was : should be written as,
> > >
> > > Option_A: \field{type} field indicates so-n-so...
> > > or
> > > Option_B: \field{type} indicates so-n-soo..
> >
> > Ah.
> >
> > I don't really feel adding "field" adds much, because of italics and because
> > one can see it's a field from the name.
> > So, brevity wins.
>
> Ok. Got it.
> The current patch is discussion does not have word 'field'.
> So current patch is good as-is.
> Thanks.
Agreed.
prev parent reply other threads:[~2024-09-11 10:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 16:52 [PATCH] device-parts: editorial: Fix metadata type name Parav Pandit
2024-09-09 14:18 ` Matias Ezequiel Vara Larsen
2024-09-10 16:46 ` Parav Pandit
2024-09-10 16:48 ` Michael S. Tsirkin
2024-09-10 16:51 ` Parav Pandit
2024-09-10 18:34 ` Michael S. Tsirkin
2024-09-10 18:54 ` Parav Pandit
2024-09-10 20:21 ` Michael S. Tsirkin
2024-09-11 3:19 ` Parav Pandit
2024-09-11 10:01 ` Michael S. Tsirkin [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=20240911060140-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=mvaralar@redhat.com \
--cc=parav@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.linux.dev \
/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.