On Tue, Sep 15, 2015 at 1:53 AM, Stephan Beal <sgb...@googlemail.com> wrote:
> Indeed, fossil's model allows any hash to be used, but it is not possible > to change the hash without a near-complete overhaul of fossil (and its > docs), nor without invalidating every repo in existence, so it's highly > unlikely to ever happen. Supporting two hash variants in one fossil binary > would likely prove to be problematic (and would require a major overhaul). > What parts of Fossil's source I have looked at seem to be well structure. I would be surprised if changing the hash algorithm required changing the internals of 1, maybe 2 functions. As for repo compatibility, if nothing else, a build option to select the hash algorithm to use. It would also be a good idea that repos using other than SHA1 have a new card in their manifests to indicate (and identify) use of a different has algorithm.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
