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

Re: Bug in "revision.c: --all adds HEAD from all worktrees" ?

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 15, 2017, 22:08 UTC
Message-ID
<xmqqtvxvyz3m.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAE5ih7_uuVVrze9gNr3JMg5HNH8eAcH_wM4wrc2kH6u=Hw0JOg@mail.gmail.com>
Luke Diamand <luke@diamand.org> writes:
Show 5 quoted lines
> Quite a few of the worktrees have expired - their head revision has
> been GC'd and no longer points to anything sensible
> (gc.worktreePruneExpire). The function other_head_refs() in worktree.c
> bails out if there's an error, which I think is the problem. I wonder
> if it should instead just report something and then keep going.

Am I correct to understand that your "git fsck" would fail because these HEAD refs used by other stale worktrees are pointing at missing objects?

What do you mean by "expired"? "Even though I want to keep using them, Git for some reason decided to destroy them." or "I no longer use them but kept them lying around."?

If the latter, I wonder "worktree prune" to remove the admininstrative information for them would unblock you?

Previous: Jeff KingNext: Luke Diamand
Message 6 of 9 in “Bug in "revision.c: --all adds HEAD from all worktrees" ?”
  1. Luke DiamandNov 13, 2017
  2. Luke DiamandNov 13, 2017
  3. Stefan BellerNov 13, 2017
  4. Luke DiamandNov 15, 2017
  5. Jeff KingNov 17, 2017
  6. Junio C HamanoNov 15, 2017
  7. Luke DiamandNov 16, 2017
  8. Ævar Arnfjörð BjarmasonMar 12, 2018
  9. Duy NguyenMar 13, 2018

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.