public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>,
	Parav Pandit <parav@nvidia.com>
Cc: "virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>,
	"mst@redhat.com" <mst@redhat.com>
Subject: Re: [PATCH v2] README.md: add example email for TC vote request
Date: Mon, 10 Mar 2025 14:23:36 +0100	[thread overview]
Message-ID: <87h641uihz.fsf@redhat.com> (raw)
In-Reply-To: <Z8bnpjiYpmiFH7+7@fedora>

On Tue, Mar 04 2025, Matias Ezequiel Vara Larsen <mvaralar@redhat.com> wrote:

> On Sat, Mar 01, 2025 at 06:08:32AM +0000, Parav Pandit wrote:
>> 
>> 
>> > From: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
>> > Sent: Thursday, February 27, 2025 8:33 PM
>> > 
>> > Acked-by: Cornelia Huck <cohuck@redhat.com>
>> > Signed-off-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
>> > ---
>> > 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..731838b 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>
>> > +To: virtio-comment@lists.linux.dev<br>
>> > +
>> > +Could please open a voting ballot for these changes?
>> > +
>> > +Fixes: https://github.com/oasis-tcs/virtio-spec/issues/NNN
>> > +</code></li>
>> >  <li>Please make sure to allow time for review between posting a comment
>> > and asking for a vote. </li>  </ol>
>> > 
>> > base-commit: 124fcd0e97f209aab19639e7369116d99ede22a2
>> > --
>> > 2.42.0
>> Reviewed-by: Parav Pandit <parav@nvidia.com>
>> 
>
> Could please open a voting ballot for these changes?
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/219 
>
> Thanks, Matias.

We can do this via a ballot; I'd also be fine doing this as an editorial
update.


  reply	other threads:[~2025-03-10 13:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 15:02 [PATCH v2] README.md: add example email for TC vote request Matias Ezequiel Vara Larsen
2025-03-01  6:08 ` Parav Pandit
2025-03-04 11:44   ` Matias Ezequiel Vara Larsen
2025-03-10 13:23     ` Cornelia Huck [this message]
2025-03-10 13:55       ` Michael S. Tsirkin
2025-03-10 15:58         ` Matias Ezequiel Vara Larsen
2025-03-10 17:38           ` 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=87h641uihz.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=mvaralar@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