From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: ab/coccicheck-incremental (was: What's cooking in git.git (Nov 2022, #01; Thu, 3))
Date: Mon, 07 Nov 2022 22:14:28 +0100 [thread overview]
Message-ID: <221107.861qqev53o.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <Y2RldUHTwNzmez73@nand.local>
On Thu, Nov 03 2022, Taylor Blau wrote:
> * ab/coccicheck-incremental (2022-11-02) 13 commits
> - spatchcache: add a ccache-alike for "spatch"
> - cocci: run against a generated ALL.cocci
> - cocci rules: remove <id>'s from rules that don't need them
> - Makefile: copy contrib/coccinelle/*.cocci to build/
> - cocci: optimistically use COMPUTE_HEADER_DEPENDENCIES
> - cocci: make "coccicheck" rule incremental
> - cocci: split off "--all-includes" from SPATCH_FLAGS
> - cocci: split off include-less "tests" from SPATCH_FLAGS
> - Makefile: split off SPATCH_BATCH_SIZE comment from "cocci" heading
> - Makefile: have "coccicheck" re-run if flags change
> - Makefile: add ability to TAB-complete cocci *.patch rules
> - cocci rules: remove unused "F" metavariable from pending rule
> - Makefile + shared.mak: rename and indent $(QUIET_SPATCH_T)
>
> "make coccicheck" is time consuming. It has been made to run more
> incrementally.
>
> Will merge to 'next'?
> source: <cover-v5-00.13-00000000000-20221101T222616Z-avarab@gmail.com>
I think it's ready for that, the v5 having hopefully solved any last
remaining nits / issues.
next prev parent reply other threads:[~2022-11-07 21:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 1:05 What's cooking in git.git (Nov 2022, #01; Thu, 3) Taylor Blau
2022-11-05 0:21 ` Philip Oakley
2022-11-05 0:26 ` Taylor Blau
2022-11-07 12:19 ` Philip Oakley
2022-11-08 21:49 ` Taylor Blau
2022-11-07 14:28 ` ab/config-multi-and-nonbool (was: What's cooking in git.git (Nov 2022, #01; Thu, 3)) Ævar Arnfjörð Bjarmason
2022-11-07 14:33 ` ab/make-bin-wrappers " Ævar Arnfjörð Bjarmason
2022-11-08 14:27 ` Jeff King
2022-11-08 21:52 ` Taylor Blau
2022-11-09 14:04 ` Jeff King
2022-11-07 21:14 ` Ævar Arnfjörð Bjarmason [this message]
2022-11-08 21:53 ` ab/coccicheck-incremental " Taylor Blau
2022-11-07 21:24 ` ab/sha-makefile-doc " Ævar Arnfjörð Bjarmason
2022-11-08 14:13 ` ab/submodule-helper-prep-only " Ævar Arnfjörð Bjarmason
2022-11-08 22:04 ` Taylor Blau
2022-11-08 14:14 ` ab/cmake-nix-and-ci " Ævar Arnfjörð Bjarmason
2022-11-08 14:49 ` Phillip Wood
2022-11-08 14:22 ` ab/misc-hook-submodule-run-command " Ævar Arnfjörð Bjarmason
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=221107.861qqev53o.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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 read-only IMAP folder(s) and NNTP newsgroup(s).