On Sun, 9 Aug 2009, Sverre Rabbelier wrote: > > Wouldn't the transport code also have to be modified? I assume git's > integrity checking would yell at if you gave it commits with > non-sha1-hashes and have no way to tell it that that hash was > calculated with a non-sha1-hash at clone time? Well, if you start introducing new hashes, the assumption is that all git's that access it would have to be updated. You certainly could never pull/push between git versions that don't know about each others hashes. But you _can_ autodetect the hash mechanism (simple: just try them all on the first object you encounter) Linus -- 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