Thus said Matt Welland on Mon, 21 Apr 2014 09:26:25 -0700: > Yes! This is fixed on latest! Any idea which commit fixes the problem?
I ran fossil bisect to figure out where the fix came into trunk [I must say, this is the first time I've used fossil bisect and it was quite handy!]. Here is the last BAD commit that had the problem: http://www.fossil-scm.org/index.html/timeline?dp=ab00f2b007d5229d And the commit just after that by drh fixes it [b4dffdac5e] It was also merged into the 1.28 branch (branch-1.28): http://www.fossil-scm.org/index.html/info/ebac09bcf72fbed9b389c07766a931264df9e304 So if you feel better sticking with with Fossil version 1.28, you can update to the latest on branch-1.28. Andy -- TAI64 timestamp: 400000005355fff8 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
