Fossil import now has a bug that it makes a repo with SHA3 hashes, but can't do incremental updates because of the SHA3 hashes. My workaround is to first `fossil new --sha1` and then import. The initial empty checkin is annoying for importing.
2017-08-17 18:32, Stephan Beal: > Fwiw: My recollection and opinion are the same. > > ----- stephan > Sent from a mobile device, possibly from bed. Please excuse brevity, > typos, and top-posting. > > On Aug 17, 2017 07:35, "Andy Bradford" <[email protected] > <mailto:[email protected]>> wrote: > > Thus said Andy Goth on Wed, 16 Aug 2017 10:47:56 -0500: > > > What of this old thread? Are the issues it discusses still pertinent, > > or have they been resolved? > > I believe all the relevant issues were actually resolved, however, I > think it was still unfavorable given the time that was available for > testing the changes before release. > > Personally, I would be in favor of retaining the old behavior by > default, but allowing a command line option to ``fossil init'' that > would initialize a new repository without it. > > Andy > -- > TAI64 timestamp: 4000000059952b4d > > > _______________________________________________ > fossil-users mailing list > [email protected] > <mailto:[email protected]> > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > <http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users> > > > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
