Thanks for the help, all. I still don't completely understand what happened but things are sane again!
On Wed, Nov 29, 2017 at 4:11 PM Joerg Sonnenberger <jo...@bec.de> wrote: > On Wed, Nov 29, 2017 at 12:02:11PM -0500, Richard Hipp wrote: > > On 11/29/17, Jacob MacDonald <jaccar...@gmail.com> wrote: > > > Ah, I see. It seems strange to me that the policy didn't get set when I > > > cloned. How can I avoid the same thing in the future and is there any > way > > > to change the artifacts in the local repository to SHA3? > > > > There is no good way to change historical artifacts from SHA1 to SHA3. > > There could be a loss-less one-time migration of the whole repo and even > an incremental mirror mode that supports keeping SHA1 and SHA3 repos in > sync. It's certainly much simpler than keeping a git mirror in-sync :) > > Joerg > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
