git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] branch: avoid slow strvec Coccinelle matching

From
EUEmmanuel Ugwu <emmanuelugwu121@gmail.com>
Date
Sep 4, 2026, 04:20 UTC
Message-ID
<CALk1092+d4kazT-cQuN3Xih2cJNBC8mBAbyR0YPELWT37K9KDg@mail.gmail.com>
In-Reply-To
<20260726074122.GB2366012@coredump.intra.peff.net>
Hi Junio, Jeff,

I'm Emmanuel Ugwu, new to the project and looking to get involved. I noticed this #leftoverbits from <https://github.com/pabloosabaterr/WhatToGit/blob/main/leftoverbits.md>. I have gone through the thread, the desired fix is to fix the inconsistencies in type by choosing/using a wide-enough type to avoid overflow (size_t) right?

Is now a reasonable time to start looking into this, or would you rather it wait until 'hn/branch-delete-merged' has settled?

Thanks, Emmanuel Ugwu

On Sun, Jul 26, 2026 at 8:41 AM Jeff King <peff@peff.net> wrote:
Show 18 quoted lines
>
> On Fri, Jul 24, 2026 at 10:33:05AM -0700, Junio C Hamano wrote:
>
> > Here is what I recommend that we do.  In the short term, i.e.,
> > within the context of the topic in question, let's use 'int' to
> > match the type used to count the members of an array embedded in
> > 'struct ref_array'.
> >
> > But let's leave a '#leftoverbits' note here in the mailing list
> > archive to remind us to revisit the idea of consistently using
> > 'size_t' to count things when things are quiet.  This is not the
> > time to needlessly disrupt the 'hn/branch-delete-merged' topic, I
> > think.
>
> Yep, agreed on all points.
>
> -Peff
>
Previous: Jeff KingNext: Jeff King
Message 8 of 11 in “branch: avoid slow strvec Coccinelle matching”
  1. branch: avoid slow strvec Coccinelle matchingtnyman@openai.com, Jul 24, 2026
  2. Jeff KingJul 24, 2026
  3. Harald NordgrenJul 24, 2026
  4. Junio C HamanoJul 24, 2026
  5. Junio C HamanoJul 24, 2026
  6. Junio C HamanoJul 24, 2026
  7. Jeff KingJul 26, 2026
  8. Emmanuel UgwuSep 4, 2026
  9. Jeff KingJul 26, 2026
  10. Junio C HamanoJul 24, 2026
  11. Taylor BlauJul 24, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.