Phil Lawrence <prlawrence@xxxxxxxxx> writes: > One approach might be to first generate a state-of-the-repo SHA1: > # http://stackoverflow.com/a/7350019/834039 > # http://git-scm.com/book/ch9-2.html > { > git rev-list --objects --all > git rev-list --objects -g --no-walk --all > git rev-list --objects --no-walk \ > $(git fsck --unreachable | > grep '^unreachable commit' | > cut -d' ' -f3) > } | sort | uniq | git hash-object -w --stdin I think you'd only need to record the state of all refs (eg. the output of `git for-each-ref') to reliably detect any changes. Andreas. -- Andreas Schwab, schwab@xxxxxxxxxxxxxx GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- 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