git gc and worktrees

From: Johannes Sixt <j6t@kdbg.org>
Date: May 31, 2016, 07:07 UTC
Message-ID: <574D382A.8030809@kdbg.org>

Earlier this year I had a largish merge going on in a separate worktree. With a mix of staged resolutions and unmerged paths in the index, I ran 'git gc' in the main worktree. This removed a lot of objects that were recorded in that separate worktree index. (I was able to recover them because the content was still on disk.)

Now I wanted to derive a test case that shows that breakage, but I am unable to. The objects recorded in a separate worktree index, but not committed, yet, are not pruned anymore.

Have there been any fixes in this regard recently? Or does this look like something else going on?

-- Hannes

$ 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.