From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: Akihiko Odaki <akihiko.odaki@daynix.com>,
Bibo Mao <maobibo@loongson.cn>,
Peter Maydell <peter.maydell@linaro.org>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: Giving your own patches your Reviewed-by
Date: Wed, 12 Mar 2025 11:18:59 +0100 [thread overview]
Message-ID: <33ac4559-462a-4623-ae19-517ccf64381e@linaro.org> (raw)
In-Reply-To: <878qpamvk6.fsf@pond.sub.org>
On 12/3/25 10:45, Markus Armbruster wrote:
> I stumbled over commits that carry the author's Reviewed-by.
>
> There may be cases where the recorded author isn't the lone author, and
> the recorded author did some meaningful review of the patch's parts that
> are not theirs. Mind that we do need all authors to provide their
> Signed-off-by.
>
> When the only Signed-off-by is from the recorded author, and there's
> also their Reviewed-by, the Reviewed-by is almost certainly bogus.
>
> Now, accidents happen, no big deal, etc., etc. I post this to hopefully
> help reduce the accident rate :)
>
> Here's my quick & sloppy search for potentially problematic uses of
> Reviewed-by:
>
> $ git-log --since 'two years ago' | awk -F: '/^commit / { commit=$0 } /^Author: / { guy=$2 } /^ Reviewed-by: / { if ($2 == guy) { print commit; print guy } }'
>
Since you are looking at this, it reminds me an orthogonal discussion
we refresh from time to time at the KVM forum conference: is it OK to
merge unreviewed patches?
next prev parent reply other threads:[~2025-03-12 10:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 9:45 Giving your own patches your Reviewed-by Markus Armbruster
2025-03-12 10:03 ` Philippe Mathieu-Daudé
2025-03-12 10:10 ` Markus Armbruster
2025-03-12 10:13 ` Daniel P. Berrangé
2025-03-12 12:54 ` Yi Liu
2025-03-13 6:45 ` CLEMENT MATHIEU--DRIF
2025-03-13 7:13 ` Markus Armbruster
2025-03-12 10:18 ` Philippe Mathieu-Daudé [this message]
2025-03-12 10:55 ` Markus Armbruster
2025-03-12 10:45 ` Daniel P. Berrangé
2025-03-12 10:56 ` Philippe Mathieu-Daudé
2025-03-13 1:21 ` bibo mao
2025-03-13 5:32 ` Markus Armbruster
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=33ac4559-462a-4623-ae19-517ccf64381e@linaro.org \
--to=philmd@linaro.org \
--cc=akihiko.odaki@daynix.com \
--cc=armbru@redhat.com \
--cc=maobibo@loongson.cn \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).