From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] Re: [virtio-comment] [PATCH v2] virtio-gpio: add formal specification
Date: Wed, 14 Jul 2021 03:40:15 -0400 [thread overview]
Message-ID: <20210714032108-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <641254c3-d60d-eb17-7388-29dd9ebcb826@metux.net>
On Wed, Jun 30, 2021 at 05:55:07PM +0200, Enrico Weigelt, metux IT consult wrote:
> On 30.06.21 17:22, Viresh Kumar wrote:
> > + All the people from previous version (Please cc them yourself while sending a
> > new version, these are the people interested in this stuff).
>
> Phuh, it's hard to track them all. I'm assuming everybody interested in
> this is already on the list or can easily subscribe :p
It's a matter of courtesy to help people who contributed by
spending time on review locate your new version.
Tracking what changed to address which comments and listing
that in the cover letter is also very much expected of contributors.
Please do this in the future.
--
MST
---------------------------------------------------------------------
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:[~2021-07-14 7:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 11:58 [virtio-comment] [PATCH v2] virtio-gpio: add formal specification Enrico Weigelt, metux IT consult
2021-06-30 15:22 ` [virtio-dev] " Viresh Kumar
2021-06-30 15:55 ` Enrico Weigelt, metux IT consult
2021-06-30 17:30 ` [virtio-comment] " Viresh Kumar
2021-07-01 9:01 ` Arnd Bergmann
2021-07-01 14:43 ` Enrico Weigelt, metux IT consult
2021-07-01 16:51 ` Viresh Kumar
2021-07-07 5:04 ` Viresh Kumar
2021-07-01 14:21 ` [virtio-comment] " Enrico Weigelt, metux IT consult
2021-07-01 16:09 ` Viresh Kumar
2021-07-14 7:40 ` 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=20210714032108-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=lkml@metux.net \
--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