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

Re: [PATCH v3] reflog: close leak of reflog expire entry

From
Jeff King <peff@peff.net>
Date
Jul 22, 2025, 23:10 UTC
Message-ID
<20250722231019.GA1598@coredump.intra.peff.net>
In-Reply-To
<xmqqms8wuxkf.fsf@gitster.g>
On Tue, Jul 22, 2025 at 07:09:20AM -0700, Junio C Hamano wrote:
Show 14 quoted lines
> Jeff King <peff@peff.net> writes:
> 
> > Subject: [PATCH] t1410: add test of gc.<pattern>.reflogExpire config
> >
> > We have long supported the ability to set reflog expiration config for
> > individual, going back to 3cb22b8efe (Per-ref reflog expiry
> > configuration, 2008-06-15). But we have never had any tests.
> 
> Yikes.  I completely forgot adding that feature, but it seems I also
> forgot to add tests when I added it.  My bad.
> 
> "individual" -> "individual refs" or something?  I was confused
> after my initial read, which sounded as if we are talking about
> allowing individual users to set the configuration variable ;-)

Yep, exactly. I admit I didn't spend as much time on the commit message for this one, since I figured it might just get squashed anyway. :)

-Peff
Previous: Junio C HamanoNext: Jacob Keller
Message 4 of 8 in “reflog: close leak of reflog expire entry”
  1. reflog: close leak of reflog expire entryJacob Keller, Jul 21, 2025
  2. Jeff KingJul 22, 2025
  3. Junio C HamanoJul 22, 2025
  4. Jeff KingJul 22, 2025
  5. Jacob KellerJul 22, 2025
  6. Junio C HamanoJul 22, 2025
  7. Jacob KellerJul 22, 2025
  8. Junio C HamanoJul 22, 2025

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.