On 3/3/17, Ramon Ribó <ram...@compassis.com> wrote: > > I think it is more clear and simple a "fossil rebuild --sha3"
Rebuilding does not change hashes. You cannot change the hashes, as doing so would change the name of historical check-ins. So if you have 10 years of check-in history with SHA1 names, those will either need to all be renamed (which will break historical hyperlinks) or just keep them as SHA1 and move forward with SHA3-256. But if the rule is that the child is always the same hash as the parent, you have to have some way of making an exception so that you can start using SHA3-256. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
