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 16, 2010, 01:37 UTC
Message-ID
<7vljcogot1.fsf@alter.siamese.dyndns.org>
In-Reply-To
<alpine.LFD.2.00.1004152059100.7232@xanadu.home>
Nicolas Pitre <nico@fluxnic.net> writes:
> Again, keeping reflogs 90 days for stuff that is _already_ reachable 
> through existing refs is much less useful than keeping otherwise 
> unreachable stuff 90 days.  So I still don't see the point of this 
> eagerness to prune deleted stuff faster.

Hmph, I honestly cannot care about this very much without knowing where this is going, because the distinction between the two has been with us practically forever, since the day one of "reflog expire".

Is there any constructive conclusion you are aiming for? For example, is a proposal to update the default value of both to 90 or 120 days coming?

FWIW, I have this in my primary repository.
    [gc]
            packrefs = no
            reflogexpire = '2005-01-01 00:00:00 +0000'
            reflogexpireunreachable = '2005-01-01 00:00:00 +0000'
Previous: Nicolas PitreNext: Nicolas Pitre
Message 13 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.