> Since sending the previous, I've reconsidered and would now like to
> release Fossil 2.0 and Fossil 2.1 simultaneously. The only
> difference between these two version will be that Fossil 2.0 still
> always generates SHA1 hashes on new content whereas Fossil 2.1
> generates only SHA3 hashes. But both version understand SHA3
> hashes.
> Notice the subtle change in Fossil 2.0. Instead of generating
> either SHA1 or SHA3 hashes depending on what it has seen before, 2.0
> now always generates only SHA1 hashes. Unconditionally.
Ok, that answers the question I just posted, so my previous mail can
be considered a "nevermind".
--
So long,
Andreas Kupries <akupr...@shaw.ca>
<http://core.tcl.tk/akupries/>
Developer @ Hewlett Packard Enterprise
-------------------------------------------------------------------------------
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
