On Fri, Sep 11, 2015 at 6:57 PM, Warren Young <w...@etr-usa.com> wrote: > > I wonder if this is an implementation detail leaking through into the UI, > though. Under what conditions, except for Noam’s contrived example with > hardcoded dates, is there a useful distinction between “hash” — implying a > number that you could reliably recompute given all the input data — and > “random number”? > > Short of crawling the DB, you don’t have all the input data, so what does > it matter how that hex string was computed?
It is an implementation detail leaking through, but with a mitigating reason. One of the things many people don't like about DVCSs in general is the long commit IDs. They will ask why isn't it a small number like, for example, SVN uses. Then they ask how do we know it's really unique? By telling them (in simplified terms) how it is computed, they more readily accept the need for such large IDs.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
