On Fri, Aug 24, 2012 at 07:32:18PM +0200, Stephan Beal wrote: > On Fri, Aug 24, 2012 at 6:57 PM, Richard Hipp <d...@sqlite.org> wrote: > > > Apparently when it looked at the file that was committed to the repository > > as "mefs1a.c" that file was different from what it saw on disk. The > > version of the file that it tried store in the repository is now copied > > into file-15c57bdd987a757d. Can you run a diff on "mefs1a.c" and > > "file-15c57bdd987a757d" and let us know how they differ? > > > > Can this be caused by a particularly slow disk cache or similar? My netbook > started (just recently) behaving similarly oddly - after a rebuild, if i > run the new binary within 1-2 seconds of build completion, i get the OLD > binary state. if i wait 3 seconds or so i get the right one.
Very weird. What OS works so bad? The filesystem has traditionally been a kind of IPC, and in your situation, that can't work at all. I've seen a message like that if I ever change a file *while* editting the commit message. Can it be the case? _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
