On Tue, Feb 28, 2017 at 7:49 PM, Richard Hipp <d...@sqlite.org> wrote:
> > (2) Usually only the first 40 digits of SHA3 hashes will be displayed, > especially on space-constrained tty output. > A question on the "Usually" part, mainly for clarification. Fossil will currently display only as many characters as needed for the hash so that the hash is "unique" in the repository. So, IF (yes, it is a big if :-) ) there is a SHA1 hash and a SHA3 hash where the first 40 characters match then Fossil will display the first 41 characters of the SHA3 hash. Is this correct? Also are there any thoughts on about a "rehash" command that would go through the repository and change all the SHA1 hashes to SHA3? Will there be any measurements taken to find out how much of an impact there will be to the repository by changing to SHA3? Things like repository size, rebuild time, and other more interesting details. I ask only out of curiosity, not that I think it will be an issue. _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
