Shawn Pearce <spearce@xxxxxxxxxxx> writes: > Junio C Hamano <junkio@xxxxxxx> wrote: >> I personally am not interested in making this configurable at >> all. The hashcmp() change on the other hand to abstract out 20 >> was a good preparation, if we ever want to switch to longer >> hashes we would know where to look. > > What about all of those memcpy(a, b, 20)'s? :-) Surely. If you are inclined to, go wild. > I can see us wanting to support say SHA-128 or SHA-256 in a few > years. Especially as processors get faster and better attacks are > developed against SHA-1 such that its no longer really the best > trade-off hash function available. - 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