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, 07:40 UTC
Message-ID
<7vochlkvtg.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4BC6B5FF.6030406@viscovery.net>
Johannes Sixt <j.sixt@viscovery.net> writes:
> Does not help what? What is the problem?

You will lose the record from HEAD reflog that records the fact that you were at the tip of "next" less than "reflogexpire" but more than "reflogexpireunreachable" time ago, if you run "gc" while on "master".

Such a pruning does not have much to do with the real reason why expireunreachable would be a useful thing (namely, to prune failed histories that have been rewound away faster than the history that survived from reflog of individual branches).

Previous: Johannes SixtNext: Johannes Sixt
Message 4 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.