On Wed, 7 Jun 2006, Kenneth Johansson wrote: > > Iwas doing a git pull that ended badly and I thought that just redoing the > command may help but then git thinks everything is just fine. What happened is that your first pull actually worked fine, but the final "git-diff-tree" that shows what the pull actually _did_ ended up SIGSEGV'ing. Subsequent pulls won't SIGSEGV, because they dont' have anything to do any more: your state is fine. I think the SIGSEGV was due to the problem (that Junio already fixed) with a corrupted heap due to the "diffstat" doing bad things for renames. So you probably do want to update your git version, but I don't think anything bad actually ever happened, apart from the (a) scare and (b) lack of diffstat output after the pull. > After a few failed attempts I still have not find a good way to make sure > that everything is indeed correct. What is the suggested commands to do > that ? In the future, just do "git fsck-objects --full" if you're nervous. That will do a full integrity check. Linus - : 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