From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
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 10:52:21 -0700 [thread overview]
Message-ID: <xmqq7blx7tii.fsf@gitster.g> (raw)
In-Reply-To: <anlj3kdAfOh8OnNR@pks.im> (Patrick Steinhardt's message of "Mon, 10 Aug 2026 07:38:38 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> 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?
We still do catch when somebody writes "if (a == NULL)", no?
next prev parent reply other threads:[~2026-08-10 17:52 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
2026-08-10 17:52 ` Junio C Hamano [this message]
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=xmqq7blx7tii.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
--cc=ps@pks.im \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox