Re: fsck missing dangling commits that are candidate heads?

From: Nicolas Pitre <nico@cam.org>
Date: Apr 3, 2007, 19:53 UTC
Message-ID: <alpine.LFD.0.98.0704031551090.28181@xanadu.home>
In-Reply-To: <loom.20070403T213135-68@post.gmane.org>

On Tue, 3 Apr 2007, Sergio Callegari wrote:

Show 14 quoted lines

> Hi,
> 
> on git 1.5.0.6, I have done the following:
> 
> work work
> 
> git commit -a
> 
> git reset HEAD^         (assume a mistake)
> 
> git fsck
> 
> the last fsck shows nothing...
> Is this correct?

Yes.

Show 5 quoted lines

> Shouldn't the latest commit (the one made unreachable by the
> reset) be reported as dangling and as a candidate branch head?
> 
> Also git lost-found misses the commit...
> But it is there... I can find it manually in the object database and tag it.

It is not lost. Try git log -g and you'll probably find it there... at least until the reflog entry corresponding to it gets expired.

Nicolas