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

dangling commits in worktree

From
Van Oostenryck Luc <luc.vanoostenryck@gmail.com>
Date
Nov 23, 2016, 00:52 UTC
Message-ID
<CAExDi1SYOuq7GJC69+5yDmzaw--vKMmmqv0Jsm80hU1L5phDUg@mail.gmail.com>
Hi,

More or less by error I used the fsck command in a worktree and I had the surprised to see that it reported a lot of dangling commits while it was not supposed to have one. I quickly realized that it was the case only in the worktree, in the main dir things were OK. While experimenting a bit I also saw that git gc had not the same effect in a worktree than in the main tree (the pack was smaller, more files were left in objects/xx/ dirs), which is even more odd and a bit scary when thinking to the pruning.

This seems like a bug to me and googling about it didn't returned anything.
Luc Van Oostenryck
Next: Duy Nguyen
Message 1 of 3 in “dangling commits in worktree”
  1. Van Oostenryck LucNov 23, 2016
  2. Duy NguyenNov 23, 2016
  3. Luc Van OostenryckNov 23, 2016

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.