Greg Stein wrote:
> We *still* have all the problems that md5 is fully-intertwined in our
> code. I'm still not willing to do double-checksums and kill millions
> of coders for a few researchers who could simply tar their candidate
> pairs together, or gzip them. Yes, that's the brutal truth :-P ... the
> researchers need to use workarounds, and the millions get a fast
> product.
Please forgive my ignorance in this matter, but when you look at a typical
profile -- from a user's perspective -- of Subversion's bottlenecks, will a
second hash calculation even register? Surely network turnarounds and
working copy I/O dwarf this additional calculation in terms of cost to the
user's time. Don't they? Keep in mind that this calculation is only ever
made at commit time, too. It isn't as if we trade in SHA1 currency all over
the place.
--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2008-10-22 14:49:12 CEST