On Tue, 3 Apr 2007, Sergio Callegari wrote: > 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. > 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 - 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