On Mar 6, 2017, at 12:21 AM, Tino Lange <tino.la...@interactivedata.com> wrote: > > Now that Fossil 2.0 is out I wonder if line 42 here: > https://www.fossil-scm.org/index.html/artifact?ln=on&name=f23144d54a286503 > should be turned to 1 to change the mv-and-rm behaviour?
While I would like to see that behavior become the default, too, I can forgive the Fossil developers for indicating at one point that this behavior would change at “Fossil 2.0”, since they clearly had no idea at the time that they’d be using that number for something entirely different. Maybe for Fossil 2.2, though, after all this SHA3 brouhaha quiets down, and after the Fossil devs have had time to clear the backlog of SQLite issues that have built up as a result of this digression? I’ve been running my Fossil binaries configured like this for a couple of years now, probably. There have been no serious problems. I put the qualifier in there because Fossil isn’t always smart about mv --hard in the face of multiple files. I’ve found it best to wrap such things up in a “for” loop at the shell prompt whenever I’m doing something the slightest bit tricky. (Sorry, no simple test case available at this time.) _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
