From: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtio-comment@lists.linux.dev, cohuck@redhat.com, parav@nvidia.com
Subject: Re: [PATCH v4] README.md: add example email for TC vote request
Date: Wed, 12 Mar 2025 10:09:49 +0100 [thread overview]
Message-ID: <Z9FPXdEPneX0azfg@fedora> (raw)
In-Reply-To: <20250311180828-mutt-send-email-mst@kernel.org>
On Tue, Mar 11, 2025 at 06:09:36PM -0400, Michael S. Tsirkin wrote:
> On Tue, Mar 11, 2025 at 10:20:30PM +0100, Matias Ezequiel Vara Larsen wrote:
> > Signed-off-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
> > ---
> > v3 -> v4: add "[]"
> > v2 -> v3: use "()"
> > v1 -> v2: add Subject and To
> > ---
> > README.md | 11 ++++++++++-
> > 1 file changed, 10 insertions(+), 1 deletion(-)
> >
> > diff --git a/README.md b/README.md
> > index c06caf6..f4b32ab 100644
> > --- a/README.md
> > +++ b/README.md
> > @@ -206,7 +206,16 @@ The mail requesting the vote should include the following, on a line by itself:<
> > <code>
> > Fixes: https://github.com/oasis-tcs/virtio-spec/issues/NNN
> > </code>
> > -(NNN is the issue number)</li>
> > +(NNN is the issue number)<br>
> > +For example, you can use the following template when requesting the TC vote:<br>
> > +<code>
> > +Subject: [PATCH] (description of changes)<br>
>
> Wait wait, this should be in response to the patch, no?
>
> Subject: Re: [PATCH] (description of changes)<br>
> In-Reply-To: (message id of the patch)
>
>
The patch introduces a template to ensure that when requesting to open a
ballot, people include in the message both the GitHub issue link and the
request itself. Do you think Subject and In-Reply-To are important in
this context?
Matias
next prev parent reply other threads:[~2025-03-12 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 21:20 [PATCH v4] README.md: add example email for TC vote request Matias Ezequiel Vara Larsen
2025-03-11 22:09 ` Michael S. Tsirkin
2025-03-12 9:09 ` Matias Ezequiel Vara Larsen [this message]
2025-03-12 11:23 ` Michael S. Tsirkin
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=Z9FPXdEPneX0azfg@fedora \
--to=mvaralar@redhat.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=parav@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox