I was wondering if there is a quick way to identify commits that reference missing trees or blobs as identified by git fsck? This would be quite useful in situations where one is trying to salvage as much history as possible from a damaged repository. jon. -- 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