From: Junio C Hamano <gitster@pobox.com>
To: Glen Choo <chooglen@google.com>
Cc: git@vger.kernel.org, "Taylor Blau" <me@ttaylorr.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Elijah Newren" <newren@gmail.com>
Subject: Re: How do we review changes made with coccinelle?
Date: Fri, 31 Mar 2023 11:17:48 -0700 [thread overview]
Message-ID: <xmqqedp4g4z7.fsf@gitster.g> (raw)
In-Reply-To: <kl6lzg7sc01z.fsf@chooglen-macbookpro.roam.corp.google.com> (Glen Choo's message of "Fri, 31 Mar 2023 10:17:44 -0700")
Glen Choo <chooglen@google.com> writes:
> I agree, but I wonder what this means in practice when .cocci fluency is
> so low. Maybe:
>
> - We increase .cocci fluency, partly by creating our own learning
> materials, partly by being more conscious about spreading knowledge
> from the folks who are relatively fluent in it. We might not have to
> do a lot to get the ball rolling either; just checking in a
> "MyFirstCocci" would help a lot, I think.
I think it goes both ways. Readers of course must be willing to
learn, but whoever proposes to add a .cocci patch file should be
able to explain what the rewrite rules in there are designed to do
and why. It is pretty much the same deal as any other patches.
I'll wait and prefer to hear from others, also on points that I did
not even quote back in my message because I didn't have anything to
add myself, before digging further on points I responded to.
Thanks for starting this topic.
next prev parent reply other threads:[~2023-03-31 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 18:23 How do we review changes made with coccinelle? Glen Choo
2023-03-30 19:13 ` Junio C Hamano
2023-03-31 17:17 ` Glen Choo
2023-03-31 18:17 ` Junio C Hamano [this message]
2023-03-31 23:49 ` Taylor Blau
2023-03-31 23:53 ` Taylor Blau
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=xmqqedp4g4z7.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
--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 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).