On 3/9/17, Warren Young <[email protected]> wrote: >Our newbie may be setting up a repo that > they know needs to be accessible to Fossil 1.x clients, and they can’t force > the upgrade.
Our newbie is going to need to know about the --sha1 option to "fossil new". Otherwise, the initial check-in created will use a SHA3 hash and the whole repository will be inaccessible to older clients. Adding a method to change the hash-policy later won't help that. -- D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
