{"thread":{"id":"44537","subject":"dangling commits in worktree","startedAt":"2016-11-23T00:52:34Z","lastAt":"2016-11-23T14:15:15Z","messageCount":3,"participants":["Van Oostenryck Luc","Duy Nguyen","Luc Van Oostenryck"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"306368","messageId":"CAExDi1SYOuq7GJC69+5yDmzaw--vKMmmqv0Jsm80hU1L5phDUg@mail.gmail.com","threadId":"44537","inReplyTo":null,"subject":"dangling commits in worktree","fromName":"Van Oostenryck Luc","fromEmail":"luc.vanoostenryck@gmail.com","sentAt":"2016-11-23T00:52:02Z","receivedAt":"2016-11-23T00:52:34Z","isPatch":false,"sender":{"key":"luc.vanoostenryck@gmail.com","avatar":"https://avatars.githubusercontent.com/u/16168334?v=4"},"body":"Hi,\n\nMore or less by error I used the fsck command in a worktree and I had\nthe surprised to see that it reported a lot of dangling commits while it was\nnot supposed to have one.\nI quickly realized that it was the case only in the worktree, in the main dir\nthings were OK. While experimenting a bit I also saw that git gc had not the\nsame effect in a worktree than in the main tree (the pack was smaller, more\nfiles were left in objects/xx/ dirs), which is even more odd and a bit\nscary when thinking to the pruning.\n\nThis seems like a bug to me and googling about it didn't returned anything.\n\nLuc Van Oostenryck\n"},{"id":"306373","messageId":"CACsJy8CPX3PDfhcaftDHy_U37rEACr7Q1gj_un4ALen45J9GZQ@mail.gmail.com","threadId":"44537","inReplyTo":"CAExDi1SYOuq7GJC69+5yDmzaw--vKMmmqv0Jsm80hU1L5phDUg@mail.gmail.com","subject":"Re: dangling commits in worktree","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2016-11-23T09:45:56Z","receivedAt":"2016-11-23T09:48:11Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Wed, Nov 23, 2016 at 7:52 AM, Van Oostenryck Luc\n<luc.vanoostenryck@gmail.com> wrote:\n> Hi,\n>\n> More or less by error I used the fsck command in a worktree and I had\n> the surprised to see that it reported a lot of dangling commits while it was\n> not supposed to have one.\n> I quickly realized that it was the case only in the worktree, in the main dir\n> things were OK. While experimenting a bit I also saw that git gc had not the\n> same effect in a worktree than in the main tree (the pack was smaller, more\n> files were left in objects/xx/ dirs), which is even more odd and a bit\n> scary when thinking to the pruning.\n>\n> This seems like a bug to me and googling about it didn't returned anything.\n\nIt's a known issue that gc (and maybe some others that do rev-list\n--all, like fsck) \"forgets\" about some worktree's refs and you will\nsee what you see. Work on it was postponed because the \"refs\"\nsubsystem was being refactored. I think I'm resuming it soon.\n-- \nDuy\n"},{"id":"306376","messageId":"20161123141502.GA10722@macbook.local","threadId":"44537","inReplyTo":"CACsJy8CPX3PDfhcaftDHy_U37rEACr7Q1gj_un4ALen45J9GZQ@mail.gmail.com","subject":"Re: dangling commits in worktree","fromName":"Luc Van Oostenryck","fromEmail":"luc.vanoostenryck@gmail.com","sentAt":"2016-11-23T14:15:03Z","receivedAt":"2016-11-23T14:15:15Z","isPatch":false,"sender":{"key":"luc.vanoostenryck@gmail.com","avatar":"https://avatars.githubusercontent.com/u/16168334?v=4"},"body":"On Wed, Nov 23, 2016 at 04:45:56PM +0700, Duy Nguyen wrote:\n> \n> It's a known issue that gc (and maybe some others that do rev-list\n> --all, like fsck) \"forgets\" about some worktree's refs and you will\n> see what you see.\n\nGood. I just wanted to be sure it was a known problem.\nThanks for the info.\n\nLuc\n"}]}