From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
git@vger.kernel.org, tnyman@openai.com,
Taylor Blau <me@ttaylorr.com>, Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH 2/2] ci: bump ubuntu image version for static-analysis job
Date: Mon, 10 Aug 2026 07:38:38 +0200 [thread overview]
Message-ID: <anlj3kdAfOh8OnNR@pks.im> (raw)
In-Reply-To: <xmqq8q6hgb2m.fsf@gitster.g>
On Fri, Aug 07, 2026 at 09:16:49AM -0700, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
>
> > They'd of course require a bit of a deeper look, but that could be
> > another way to speed up Coccinelle for us. Even though I cannot say for
> > sure by how much, I didn't give it a test.
>
> Another benefit is that it would reduce the programmer's burden, as
> it is not immediately apparent which rules are still relevant.
>
> I wonder if we can easily define the exit criteria when we introduce
> a new rule and document them, immediately next to the rules.
>
> You said "refs, object_id, the_repository, ... all look like we have
> long done with the migrations"; in retrospect, would it have been
> easily doable for those who introduced these rules to describe how
> we would declare "now migration is done"? If so, perhaps a good
> step forward may be to update tools/coccinelle/README to add such a
> rule.
>
> ... goes and looks ...
>
> The readme file clearly states that transformations needed for
> migrations are *not* regularly run. Is it possible that we have
> these rules you mentioned misclassified?
For all I can see, both our Makefile and Meson simply take all
Coccinelle files we have, concatenate and run those rules against our
whole codebase. So I don't see any kind of classification at all?
Ah, no, you're right. We have the ".pending" suffix that we do treat
special. We only have a single one of those with "config_fn_ctx".
Arguably, many of the others should've been classified as pending, too.
But I think it's quite easy to miss that we even treat these kinds of
files special.
Taking a step back, I do have to wonder whether the Cocci files have
been adding any kind of value in the first place. I myself introduced
some of them in contexts where I made sweeping changes to our APIs, so
that any in-flight topics can be trivially adjusted via Coccinelle. But
I very much doubt that anyone ever used those to adapt their in-flight
patch series at all.
So maybe we should just not do that anymore?
Patrick
next prev parent reply other threads:[~2026-08-10 5:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 8:32 [PATCH 0/2] bump static-analysis ci image version Jeff King
2026-07-26 8:37 ` [PATCH 1/2] bloom: silence CHECK_ASSERTION_SIDE_EFFECTS false positive Jeff King
2026-07-26 8:39 ` [PATCH 2/2] ci: bump ubuntu image version for static-analysis job Jeff King
2026-08-07 10:24 ` Patrick Steinhardt
2026-08-07 16:16 ` Junio C Hamano
2026-08-10 5:38 ` Patrick Steinhardt [this message]
2026-08-10 17:52 ` Junio C Hamano
2026-08-11 5:02 ` Patrick Steinhardt
2026-08-07 16:47 ` Elijah Newren
2026-08-08 17:31 ` SZEDER Gábor
2026-07-26 16:34 ` [PATCH 0/2] bump static-analysis ci image version Junio C Hamano
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=anlj3kdAfOh8OnNR@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
--cc=tnyman@openai.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.