Richard Hipp schrieb:
(...) > >>> Does anybody have any other suggestions on how to prevent the lose > >>> of uncommitted work? > >> > >> Maybe not suggestion to prevent losing of uncommitted work, but I'm > >> thinking about using 'stash' in such situation. > > Perhaps Fossil could do this automatically. Whenever an 'update' would > change any locally modified file, Fossil could stash the changes away > first and inform the user. > > That's sort of what "fossil undo" does. Except it only stores the most > recent change. You are suggesting an "auto-stash" that keeps backups at > each change, and stores them in a visible place such as the stash. An > interesting idea... But only if an update would modify local uncommitted changes, I think. So if I commit every time before I update, no auto-stash would be necessary. > Would we purge the auto-stash on a commit? Or just let it grow until > the user manually purged it? No, I feel it should not purge the auto-stash on commit. It would be safer, if it has to be deleted manually. Then I have explicitely to choose that I do not those changes anymore. Fossil cannot know my intentions. And tracking all of my actions to be sure that the auto-stashed changes were really re-introduced into my working copy would be a ehrm tricky task to implement. What Fossil could do is to warn on every commit I do until those auto-stashes are dropped again (perhaps with asking for permission to proceed with current checkin in face of auto-stashes). Ciao, chi :-) _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
