Don't know, I'll have to try and see. I can't recall doing that, but it's certainly possible.
On 10/04/2013 05:12 PM, Jan Nijtmans wrote: > 2013/10/4 Ron Aaron <r...@ronware.org>: >> Indeed, it gives an empty string. > Then I have a theory what happened. My guess is that you > cloned the repository and opened it. Later you cloned the > repository again (which got different row-id's), storing it > in the exact original location. Then the row-id's of the > .fslckout database and the repository don't match any more. > > What you can do to fix this: > - fossil update trunk (find the new rowid of "trunk", and bring > the checkout there) > - fossil revert (clean up any garbage) > then do a "make" and everything else, and try the commit. > > Am I close? > > Regards, > Jan Nijtmans > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
