On Sat, Mar 04, 2017 at 03:07:04PM +0200, Tony Papadimitriou wrote: > -----Original Message----- From: Warren Young > > > > (3) New repositories are initialized using SHA3 > > Maybe there should be a “fossil init --sha1” option for the > > technologically conservative. > > Or, for practical reasons. So, I second that. > > For example, creating a new repo locally to be hosted by chiselapp (which is > still running 1.34 BTW) would fail.
In fact, it run 1.36 now (I got corrected recently when I made the same statement). For some reason, the fossil version we see on the main page is not the same as the one when you click on a public repository. > Of course, there is the option of creating on chiselapp and then cloning and > continuing from there, but it should be able to work both ways because one > may discover the problem after having done too much work locally. I'm pretty sure the chiselapp maintainer is on that list and it's probably on his plan to upgrade to fossil-2.0. If he does, problem solve, any version of fossil can sync with chiselapp. Regards, -- Martin G. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
