I've noticed that if I remove a file from a working-set without
informing fossil about it, then fossil fails when I try to commit (other
changes in the set). That's fine, but it gives an obscure message:
fossil: no such file: somefile
fossil: SQLITE_BUSY: statement aborts at 2: [ROLLBACK] cannot
complete transaction - SQL statements in progress
I would like to suggest the following:
1. addition of an "auto-remove" or similar option, which would tell
fossil to automatically perform a "fossil rm" on any file missing
in this manner. This is a bit dangerous, so it should be an
option which is normally 'false'
2. replace "no such file" with something like "It looks like the file
'somefile' has been removed. Do you want fossil to remove it from
the repository?" (unless 'auto-remove' is selected, when it would
just do that)
3. don't show SQLITE messages unless the user wants to see them,
since they are more frightening than helpful for most users.
Thoughts?
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
