On Wed, 11 Feb 2015 15:23:55 +0100, Richard Hipp <d...@sqlite.org> wrote:

On 2/11/15, j. van den hoff <veedeeh...@googlemail.com> wrote:

whatever the reason, the netbsd example (a worst case scenario, really)
would suggest to chose 12 instead of 10 as the future default length
to avoid collisions these next some hundred years.


Maybe the default prefix lengths should auto-adjust depending on the
number of artifacts in the repository?

I'd rather vote for making it possibly user-settable via `fossil set' but with a fixed default of 10 (or 12). less worry for scripts (regex can be made exactly fitting the given fixed length rather than just matching hashes of uncertain length) postprocessing the output of fossil.

regarding the surprisingly high number of 4 length 10 collisions in the netbsd repo: any explanation for this other than that we accidentally see a "one in a hundred thousand" case here? for me it somehow smells a bit like the hashes not being a random sample from the full hash space.
but that cannot be, can it?


--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to