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

Re: [PATCH] Revert "reflog expire: don't use lookup_commit_reference_gently()"

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 17, 2024, 14:56 UTC
Message-ID
<xmqqy1605ap7.fsf@gitster.g>
In-Reply-To
<20240717054555.GA547635@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> It does make me wonder if there other gaps for reflogs that point to
> non-commits. E.g., if I have a tag pointing to a blob, would we save its
> reflog entry if a reachable commit points to that blob?. I suspect not,
> as the full reachability check is very expensive.

reflog.c:should_expire_reflog_ent() says that anything that is not a commit should be expired without doing the unreachable() check, and the UE_ALWAYS flag used for that is set by the function in question. This arrangement has stayed the same since daf1d828 (reflog expire: don't use lookup_commit_reference_gently(), 2021-12-22).

Thanks.
Previous: Jeff King
Message 3 of 3 in “Revert "reflog expire: don't use lookup_commit_reference_gently()"”
  1. Revert "reflog expire: don't use lookup_commit_reference_gently()"Junio C Hamano, Jul 16, 2024
  2. Jeff KingJul 17, 2024
  3. Junio C HamanoJul 17, 2024

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.