From: Junio C Hamano <gitster@pobox.com>
To: Toon Claes <toon@iotcl.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2025, #11; Tue, 28)
Date: Fri, 31 Oct 2025 14:33:17 -0700 [thread overview]
Message-ID: <xmqqh5ve21uq.fsf@gitster.g> (raw)
In-Reply-To: <87qzuktmoc.fsf@iotcl.com> (Toon Claes's message of "Thu, 30 Oct 2025 16:49:07 +0100")
Toon Claes <toon@iotcl.com> writes:
> Hi Junio,
>
> I don't see the patch I've submitted to speed up git-last-modified in
> this report? As a follow-up to your response on v2, I did submit v3[1]
> which resolves the -Wsign-compare issues, but I forgot to Cc you. This
> version was acked by Taylor[2].
>
> King regards,
> Toon
>
> [1]: <20251023-b4-toon-last-modified-faster-v3-1-40a4ddbbadec@iotcl.com>
> [2]: <aPrCaSOA/dclWye5@nand.local>
Unfortunately, the topic breaks make coccicheck.
https://github.com/git/git/actions/runs/18981332553/job/54214401412
We'd need at least something like the attached squashed in.
builtin/last-modified.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/last-modified.c b/builtin/last-modified.c
index c271d9585b..b0ecbdc540 100644
--- a/builtin/last-modified.c
+++ b/builtin/last-modified.c
@@ -493,7 +493,7 @@ static int last_modified_init(struct last_modified *lm, struct repository *r,
if (populate_paths_from_revs(lm) < 0)
return error(_("unable to setup last-modified"));
- lm->all_paths = xcalloc(hashmap_get_size(&lm->paths), sizeof(const char *));
+ CALLOC_ARRAY(lm->all_paths, hashmap_get_size(&lm->paths));
lm->all_paths_nr = 0;
hashmap_for_each_entry(&lm->paths, &iter, ent, hashent) {
ent->diff_idx = lm->all_paths_nr++;
--
2.51.2-719-gbbf487eab4
prev parent reply other threads:[~2025-10-31 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 22:55 What's cooking in git.git (Oct 2025, #11; Tue, 28) Junio C Hamano
2025-10-29 19:10 ` [PATCH] test-tool: fix leak in delete-gpgsig command Jeff King
2025-10-29 19:35 ` Junio C Hamano
2025-10-30 15:49 ` What's cooking in git.git (Oct 2025, #11; Tue, 28) Toon Claes
2025-10-31 21:33 ` Junio C Hamano [this message]
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=xmqqh5ve21uq.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=toon@iotcl.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.