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
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Mar 13, 2018, 20:29 UTC
Message-ID
<874lljg1ns.fsf@evledraar.gmail.com>
In-Reply-To
<C62FA8BB-FDCA-4BD0-A029-74C7AB89441F@gmail.com>
On Tue, Mar 13 2018, Stan Hu jotted:
Show 7 quoted lines
> To be clear, this is how I think we got into this state:
>
> We have worktrees that are created to squash and rebase a branch. They were left around inadvertently for one reason or another.
>
> Since we were using git v2.14.3, a git gc would prune dangling objects because it never saw that a worktree still had a reference to it. Now, in git v2.15+, worktrees are examined, and a git gc won't garbage collect any objects referenced by a worktree.
>
> Another words, the failure of git v2.14 to preserve these objects caused problems with these stale worktrees with the upgrade to v2.15+.

Thanks, I hadn't dug into the root cause. Good to know it's not some failure mode we're still producing, just the result of past bugs.

Previous: Stan Hu
Message 2 of 2 in “Re: Bug in "revision.c: --all adds HEAD from all worktrees" ?”
  1. Stan HuMar 13, 2018
  2. Ævar Arnfjörð BjarmasonMar 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.