* dangling commits in worktree
@ 2016-11-23 0:52 Van Oostenryck Luc
2016-11-23 9:45 ` Duy Nguyen
0 siblings, 1 reply; 3+ messages in thread
From: Van Oostenryck Luc @ 2016-11-23 0:52 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: dangling commits in worktree
2016-11-23 0:52 dangling commits in worktree Van Oostenryck Luc
@ 2016-11-23 9:45 ` Duy Nguyen
2016-11-23 14:15 ` Luc Van Oostenryck
0 siblings, 1 reply; 3+ messages in thread
From: Duy Nguyen @ 2016-11-23 9:45 UTC (permalink / raw)
To: Van Oostenryck Luc; +Cc: Git Mailing List
On Wed, Nov 23, 2016 at 7:52 AM, Van Oostenryck Luc
<luc.vanoostenryck@gmail.com> wrote:
> 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.
It's a known issue that gc (and maybe some others that do rev-list
--all, like fsck) "forgets" about some worktree's refs and you will
see what you see. Work on it was postponed because the "refs"
subsystem was being refactored. I think I'm resuming it soon.
--
Duy
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: dangling commits in worktree
2016-11-23 9:45 ` Duy Nguyen
@ 2016-11-23 14:15 ` Luc Van Oostenryck
0 siblings, 0 replies; 3+ messages in thread
From: Luc Van Oostenryck @ 2016-11-23 14:15 UTC (permalink / raw)
To: Duy Nguyen; +Cc: Git Mailing List
On Wed, Nov 23, 2016 at 04:45:56PM +0700, Duy Nguyen wrote:
>
> It's a known issue that gc (and maybe some others that do rev-list
> --all, like fsck) "forgets" about some worktree's refs and you will
> see what you see.
Good. I just wanted to be sure it was a known problem.
Thanks for the info.
Luc
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-11-23 14:15 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-11-23 0:52 dangling commits in worktree Van Oostenryck Luc
2016-11-23 9:45 ` Duy Nguyen
2016-11-23 14:15 ` Luc Van Oostenryck
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).