On Sun, May 22, 2011 at 12:04 AM, chi <ml-fos...@qiao.in-berlin.de> wrote:
> > > Ron Wilson schrieb: > > On Sat, May 21, 2011 at 4:29 PM, Gour-Gadadhara Dasa <g...@atmarama.net> > wrote: > > > >> On Sat, 21 May 2011 14:32:34 -0400 > >> Richard Hipp <d...@sqlite.org> wrote: > >> > >>> 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... Would we purge the auto-stash on a commit? Or just let it grow until the user manually purged it? -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
