Richard's question regarding a multi level undo, and when to purge, got
me thinking; and I apologize for posting mid - thought stream ...

 

What if fossil kept track of all the commands issued that change either
the repository or the working files. 

Obviously, it already does this at some level (commits and merges); in
the case of a revert (or even an update), it would save the affected
files, perhaps by creating an automatic branch. 

Fossil now has the files but also the complete command path to reproduce
a particular scenario, which would help in debugging.

This would really fill any gap in the stated goal of never losing any
work; not only committed work, but also work in progress.

 

 

From: fossil-users-boun...@lists.fossil-scm.org
[mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Richard
Hipp
Sent: Sunday, May 22, 2011 5:51 AM
To: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!

 

 

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

Reply via email to