fsck missing dangling commits that are candidate heads?

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

And finally...

Also git gc --prune seems to miss the commit... so when we gc useless objects appear to be kept around.

Is this correct?

Thanks,

Sergio