On Tue, Mar 25, 2014 at 5:50 PM, Andy Goth <[email protected]> wrote:
> On 3/25/2014 4:40 PM, Andreas Kupries wrote: > >> On Tue, Mar 25, 2014 at 2:28 PM, Andy Goth <[email protected]> >> wrote: >> >>> Fossil uses unique prefixes of checksums as identifiers. >>> >> >> No, it does not. Fossil stores full identifiers >> > > I was referring only to the display. Full identifiers are usually shown > only in detail pages and the actual manifests. > My original idea was to show the first 10 characters of the hash in all cases and if the first 10 characters are ambiguous, show additional characters as necessary to make the hash unambiguous. But, as the longest collision I've yet seen is only 4 characters, I never have gotten around to modifying the display logic. In order to get a 10-character collision on the SHA1 hash to two check-ins, you'd need a repository with about a million check-ins (or else you'd need to be very unlucky). The TCL project has 17241 check-ins over 16 years. SQLite has 12841 check-ins in 13.8 years. Fossil has 6823 check-ins in 6.7 years. Do you see the trend? The first collision is hundreds of years away. But, yes, it would be good to go ahead and fix this..... -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
