From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: peter.maydell@linaro.org, Thomas Huth <thuth@redhat.com>,
berrange@redhat.com, qemu-devel@nongnu.org, agraf@csgraf.de,
stefanha@redhat.com, afaerber@suse.de
Subject: Re: [PATCH] docs: Add a QEMU Code of Conduct and Conflict Resolution Policy document
Date: Wed, 31 Mar 2021 20:12:51 +0100 [thread overview]
Message-ID: <87blaznn9c.fsf@linaro.org> (raw)
In-Reply-To: <20210331150527.14857-1-pbonzini@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
<snip>
> +
> +This isn't an exhaustive list of things that you can't do. Rather, take
> +it in the spirit in which it's intended—a guide to make it easier to
> +be excellent to each other.
I think a colon might work better here:
Rather, take it in the spirit in which it's intended: a guide to make it
easier to be excellent to each other.
Other that that all looks good to me.
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
next prev parent reply other threads:[~2021-03-31 19:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 15:05 [PATCH] docs: Add a QEMU Code of Conduct and Conflict Resolution Policy document Paolo Bonzini
2021-03-31 15:47 ` Thomas Huth
2021-03-31 16:11 ` Paolo Bonzini
2021-03-31 17:01 ` David Edmondson
2021-03-31 19:12 ` Alex Bennée [this message]
2021-04-07 10:23 ` Kevin Wolf
2021-04-07 13:35 ` Alex Bennée
2021-04-07 15:42 ` Kevin Wolf
2021-04-07 16:03 ` Daniel P. Berrangé
2021-04-10 6:29 ` Thomas Huth
2021-04-13 7:42 ` Paolo Bonzini
2021-04-13 10:23 ` Andreas Färber
2021-04-13 10:24 ` Peter Maydell
2021-04-13 11:41 ` Markus Armbruster
2021-04-13 16:25 ` Daniel P. Berrangé
2021-04-13 21:16 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2021-03-29 18:01 Thomas Huth
2021-03-29 18:33 ` Daniel P. Berrangé
2021-03-29 20:59 ` Paolo Bonzini
2021-03-30 7:13 ` Thomas Huth
2021-03-30 9:59 ` Paolo Bonzini
2021-03-30 8:18 ` Daniel P. Berrangé
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=87blaznn9c.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=afaerber@suse.de \
--cc=agraf@csgraf.de \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).