From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: "Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org, "Akihiko Odaki" <akihiko.odaki@daynix.com>,
"Bibo Mao" <maobibo@loongson.cn>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Yi Liu" <yi.l.liu@intel.com>,
"Clément Mathieu--Drif" <clement.mathieu--drif@eviden.com>,
"Zhenzhong Duan" <zhenzhong.duan@intel.com>
Subject: Re: Giving your own patches your Reviewed-by
Date: Wed, 12 Mar 2025 11:10:49 +0100 [thread overview]
Message-ID: <87a59qlfti.fsf@pond.sub.org> (raw)
In-Reply-To: <9329310c-bfad-44aa-a53a-87c1f39668a2@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Wed, 12 Mar 2025 11:03:04 +0100")
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> Hi Markus,
>
(Cc'ing Yi, Clément and Zhenzhong for commit eda4c9b5b3c)
>
> 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 } }'
>
>
> Explaining some commits where I'm mentioned:
[...]
> Is this workflow making sense and accepted? Otherwise what should
> we change? Maybe clarify along with the tags; or including all
> Message-Id could make this easier to track?
The workflow is good enough as is if you ask me.
Note that the patches you quoted all have more than one Signed-off-by.
My quick & sloppy search neglects to filter these out :)
next prev parent reply other threads:[~2025-03-12 10:11 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 [this message]
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é
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=87a59qlfti.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=clement.mathieu--drif@eviden.com \
--cc=maobibo@loongson.cn \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=yi.l.liu@intel.com \
--cc=zhenzhong.duan@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.