From: Peter Maydell <peter.maydell@linaro.org>
To: bzt bzt <bztemail@gmail.com>
Cc: Andrew Baumann <Andrew.Baumann@microsoft.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] BCM2837 and machine raspi3
Date: Tue, 23 Jan 2018 18:14:06 +0000 [thread overview]
Message-ID: <CAFEAcA-1xLL1e=tyLg0d3V_PJBKjwEWNxnajTd-8trbGaR=4iw@mail.gmail.com> (raw)
In-Reply-To: <CADYoBw36gPOyiK36WaS0v_2R=iuWYL-sQAtffrZZJU2DpMv5Bw@mail.gmail.com>
On 23 January 2018 at 11:49, bzt bzt <bztemail@gmail.com> wrote:
> Hi,
>
> On Mon, Jan 22, 2018 at 1:12 PM, Peter Maydell <peter.maydell@linaro.org>
> wrote:
>> Can you send this as a proper patch email, not as a reply to
>> an existing email thread, please? (This makes our automated tooling
>> much happier.)
>
>
> Only if you're not demanding any further nonsense modifications.
I think that patch review will be much more pleasant for
both of us if you tone down the combativeness here.
Yes, sometimes code review comments aren't right because
the reviewer has missed or misunderstood a detail -- but
there's no need to throw insults around as a result.
If you don't have the time or don't want to engage with the
community's review processes, that's fine. But this hostility
is not pleasant to interact with and off-putting to other
people reading it. Please stop it.
(Sometimes a submitter doesn't have the time to work with our
review process, and that's fine. It just means that the patches
will sit on the mailing list and perhaps in future somebody
who does have the time as well as the interest in the feature
will come along and pick up the work.)
thanks
-- PMM
prev parent reply other threads:[~2018-01-23 18:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 13:20 [Qemu-devel] [PATCH] BCM2837 and machine raspi3 bzt bzt
2017-10-23 9:34 ` KONRAD Frederic
2017-10-23 12:39 ` bzt bzt
2017-10-23 16:34 ` Andrew Baumann
2017-10-24 9:53 ` bzt bzt
2017-10-24 11:05 ` BALATON Zoltan
2017-10-24 16:30 ` bzt bzt
2017-10-24 16:44 ` Andrew Baumann
2017-10-25 8:52 ` bzt bzt
2017-11-25 16:43 ` bzt bzt
2017-11-25 18:04 ` Peter Maydell
2017-11-27 19:06 ` Andrew Baumann
2017-11-28 11:26 ` bzt bzt
2017-11-28 11:56 ` Peter Maydell
2017-11-29 7:17 ` bzt bzt
2017-11-28 17:54 ` Andrew Baumann
2017-11-29 7:52 ` bzt bzt
2018-01-18 21:39 ` bzt bzt
2018-01-22 11:41 ` BALATON Zoltan
2018-01-23 11:13 ` bzt bzt
2018-01-23 11:22 ` Peter Maydell
2018-01-23 12:32 ` bzt bzt
2018-01-22 12:12 ` Peter Maydell
2018-01-23 11:49 ` bzt bzt
2018-01-23 15:09 ` BALATON Zoltan
2018-01-23 18:14 ` Peter Maydell [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='CAFEAcA-1xLL1e=tyLg0d3V_PJBKjwEWNxnajTd-8trbGaR=4iw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=Andrew.Baumann@microsoft.com \
--cc=bztemail@gmail.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).