git gc be default does only prune things older than 2 weeks so to lose your recently lost commits you would have to explicitly give a prune which is today. I d

git gc be default does only prune things older than 2 weeks so to lose your recently lost commits you would have to explicitly give a prune which is today. I do not think one can do this accidentally: git gc --prune=2012-08-05