fsck missing dangling commits that are candidate heads?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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



-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]