Thus said "j. van den hoff" on Tue, 17 Feb 2015 09:44:47 +0100: > doing the exact same cloning command after login to the server (i.e. > via a ssh connection to "itself") the clone is just fine. whether an > accidental coincidence or not: this happened today and just one day > after I updated fossil on the server and my local machine to fossil > version 1.31 [47bb6432a1] 2015-02-16 11:33:04 UTC.
I run into occasional glitches like these. Usually it turns out to be a problem with updating, building and linking in old object files. Try running ``make clean'' before building and see if it doesn't go away. Andy -- TAI64 timestamp: 4000000054e57c8a _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
