Here's what happened: I have fossil diff up in one window, and fossil commit has popped up vim to edit the commit message in another window.
I'm writing a very detailed commit message based on the diff, and I notice along the way that there's a security flaw in the code I'm about to checkin. So I fix the flaw, test the fix, and finish the commit message. Fossil apparently chokes on the fact that I changed something between the time I started the commit and the time I finished writing the message. (Which makes sense, I just didn't anticipate it.) This is the console output: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ $ fossil commit Autosync: http://---------------- Bytes Cards Artifacts Deltas Send: 130 1 0 0 Received: 414 9 0 0 Total network traffic: 328 bytes sent, 462 bytes received vi "/--------------/ci-comment-BDEC06C2866D.txt" Reading passphrase from file descriptor 3 You need a passphrase to unlock the secret key for user: "Joshua Paine <jos...@letterblock.com>" 1024-bit DSA key, ID AA5058A3, created 2010-01-15 New_Version: 03094b02bc6483cba3660069f83d50bede42790a fossil: tree checksum does not match repository after commit ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ All this makes sense, *but* now that ci-comment-BDEC06C2866D.txt file is gone with my very detailed commit message. Output of fossil version is: This is fossil version [73c24ae363] 2010-03-18 14:20:33 UTC -- Joshua Paine LetterBlock: Web applications built with joy http://letterblock.com/ 301-576-1920 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
