garbage collection - Dangling commit is not in reflog and won't purge by git gc -


I have found an inclined commitment that is not in the referral (or I use it wrong) and GIT Gc . Here's what I mean:

 % git fsck Checking directory: 100% (256/256), done. Examining the objects: 100% (5425/5425), the inclined eclipse e681384da8babd4524f545bd880dfc602d271e45 dangling drops 77835dc1395f57d359d81f2c240d02a6ff1e9a69 ...% git reflog | Grep e681% git gc Count of commodities: 5425, done. Using Delta Compression up to 4 Threads. Compressing objects: 100% (1585/1585), done. Writing the object: 100% (5425/5425), done. Total 5425 (Delta 2086), again 5425 (Delta 2086)% git is examining the fsck object directory: 100% (256/256), checking items done: 100% (5425/5425),  
 % git config gc.reflogExpireUnreacable% git will explain this for config:  

Gc.pruneExpire

I think committed is back and there is a history in the early days:

 % git log e681384da8babd4524f545bd880dfc602d271e45 --online | Tail-n2b50e1de base file structure 9a4b3af first low  

but why would not it be lacking?

I am eager to know because I am very good at not having any meaning:


Comments

Popular posts from this blog

ios - How do I use CFArrayRef in Swift? -

eclipse plugin - Run java code error: Workspace is closed -

c - Error on building source code in VC 6 -