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

Re: [PATCH 2/2] reflog: ignore expire-unreachable for "HEAD" reflog

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 15, 2010, 16:57 UTC
Message-ID
<7vhbnck618.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20100415163607.GA4279@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> I think another way of addressing the same problem would be to redefine
> "reachable" in this context as "reachable from any current ref".

I tend to agree, but I haven't thought through the case for entries that point at commits on detached HEAD. My gut feeling is that unless they are connected to a real ref by now after all these expireunreachable days, they are "failed experiments" and deserve to get pruned, so "from any ref"

Previous: Jeff KingNext: Nicolas Pitre
Message 9 of 16 in “Document gc.<pattern>.reflogexpire variables”
  1. 1/2 Document gc.<pattern>.reflogexpire variablesJunio C Hamano, Apr 14, 2010
  2. 2/2 reflog: ignore expire-unreachable for "HEAD" reflogJunio C Hamano, Apr 14, 2010
  3. Johannes SixtApr 15, 2010
  4. Junio C HamanoApr 15, 2010
  5. Johannes SixtApr 15, 2010
  6. Junio C HamanoApr 15, 2010
  7. Johannes SixtApr 15, 2010
  8. Jeff KingApr 15, 2010
  9. Junio C HamanoApr 15, 2010
  10. Nicolas PitreApr 15, 2010
  11. Junio C HamanoApr 15, 2010
  12. Nicolas PitreApr 16, 2010
  13. Junio C HamanoApr 16, 2010
  14. Nicolas PitreApr 16, 2010
  15. Johannes SixtApr 16, 2010
  16. Junio C HamanoApr 15, 2010

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.