> I was surprise that no one suggested truncating SHA-256 to 160 bits... To do that, you have to stop generating commit hashes with SHA-1, breaking compatibili

> I was surprise that no one suggested truncating SHA-256 to 160 bits... To do that, you have to stop generating commit hashes with SHA-1, breaking compatibility with existing git clients. And if you're going to do that, you might as well just use the whole SHA-256 hash, since compatibility is out the window already.