I believe so. On Wed, Nov 29, 2017, 11:13 Martin Gagnon <eme...@gmail.com> 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. > > The best policy is to let sleeping dogs lay and move on using SHA3 in > > the future. You can do that by running "fossil hash-policy sha3" on > > the local side, where you do your "fossil commit" commands. That will > > cause all future check-ins to be SHA3. > > > > I don't know how the server side got set to sha3-only. That's never > > come up before. > > Chisel have an option to upload a repository file, may be it was set to > shun-sha1 locally before to get uploaded to Chisel ? > > Is that what happened Jacob ? > > -- > Martin G. > _______________________________________________ > 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
