From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: "Glen Choo via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org, "Taylor Blau" <me@ttaylorr.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Glen Choo" <chooglen@google.com>
Subject: Re: [PATCH 0/2] cocci: codify authoring and reviewing practices
Date: Mon, 17 Apr 2023 09:21:46 -0700 [thread overview]
Message-ID: <xmqqilduo4x1.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BEWaojwSpMaYT1VqNBYuhETm-QB9UyFsC-ePsu9B_e_aQ@mail.gmail.com> (Elijah Newren's message of "Fri, 14 Apr 2023 18:27:09 -0700")
Elijah Newren <newren@gmail.com> writes:
> .... Maybe
> the wording should instead be "It's okay to give a Reviewed-by: on a
> series that also contains cocci changes when you are unfamiliar with
> coccinelle; just state that your Reviewed-by is limited to the other
> bits". Or maybe the instructions should just be to give an Acked-by.
> You should probably have someone familiar enough with coccinelle that
> they know what is worth worrying about weigh in on that aspect.
>
> But you can have my Acked-by on the other bits. :-)
The value of Reviewed-by takes two sides to determine. Even if we
reserve a Reviewed-by to "I have reviewed the entirety of this
patch, and the patch is something I can stand behind" (as opposed to
"my understanding of this patch is iffy in this and that area, but
all the other parts of the patch is something I can stand behind"),
the value of such a Reviewed-by is conditional to "how well does the
reviewer actually know the area?" A drive-by "Reviewed-by:" thrown
into a review discussion thread by a total stranger would not carry
much weight, until we know how much they are familiar with and how
good a taste they have.
And honest qualifying comments like "my understanding of this and
that area is iffy so I cannot endorse these parts" helps build trust
by others in the reviewer who gives such a partial review and we
should encourage such behaviour. I agree "Acked-by:" with comments
is a good idea.
Thanks.
next prev parent reply other threads:[~2023-04-17 16:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 20:05 [PATCH 0/2] cocci: codify authoring and reviewing practices Glen Choo via GitGitGadget
2023-04-12 20:05 ` [PATCH 1/2] cocci: add headings to and reword README Glen Choo via GitGitGadget
2023-04-12 21:18 ` Junio C Hamano
2023-04-13 18:37 ` Glen Choo
2023-04-13 18:51 ` Junio C Hamano
2023-04-12 20:05 ` [PATCH 2/2] cocci: codify authoring and reviewing practices Glen Choo via GitGitGadget
2023-04-16 7:42 ` SZEDER Gábor
2023-04-19 19:29 ` Glen Choo
2023-04-20 20:53 ` [PATCH] cocci: remove 'unused.cocci' SZEDER Gábor
2023-04-21 2:43 ` Junio C Hamano
2023-05-01 13:27 ` Ævar Arnfjörð Bjarmason
2023-05-01 15:55 ` Junio C Hamano
2023-05-01 17:28 ` Ævar Arnfjörð Bjarmason
2023-05-10 22:45 ` Junio C Hamano
2023-04-16 13:37 ` [PATCH 2/2] cocci: codify authoring and reviewing practices Ævar Arnfjörð Bjarmason
2023-04-19 22:30 ` Glen Choo
2023-04-15 1:27 ` [PATCH 0/2] " Elijah Newren
2023-04-17 16:21 ` Junio C Hamano [this message]
2023-04-27 22:22 ` [PATCH v2 " Glen Choo via GitGitGadget
2023-04-27 22:22 ` [PATCH v2 1/2] cocci: add headings to and reword README Glen Choo via GitGitGadget
2023-05-01 10:53 ` Ævar Arnfjörð Bjarmason
2023-05-01 15:06 ` Junio C Hamano
2023-05-02 19:29 ` Felipe Contreras
2023-05-02 19:30 ` Felipe Contreras
2023-05-09 17:54 ` Glen Choo
2023-04-27 22:22 ` [PATCH v2 2/2] cocci: codify authoring and reviewing practices Glen Choo via GitGitGadget
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=xmqqilduo4x1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=me@ttaylorr.com \
--cc=newren@gmail.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.