> Le 15 mai 2020 à 11:13, Tim Mackinnon <[hidden email]> a écrit :
>
> I find I do the same sort of precautionary measure (and probably would do it more if launcher supported this use case and helped me manage those snaphot images) - I view it a bit like how TimeMachine lets you see previous versions of files - yes the source code is versioned, but its just the useful execution state and window layouts that are handy to hold on to. Equally, I don't need too many of these images - and indeed want them to expire (but happy to manage that myself - its just a simple counter, or time snapshot that would make this very handy).
>
> Thanks for mentioning it Cedrick
>
> Tim
>
> On Fri, 15 May 2020, at 8:54 AM, Cédrick Béler wrote:
>> Thanks for the explanation Christophe.
>>
>> The tree might be a good idea.
>>
>>>
>>>> I actually changed once the "save as » in a « save checkpoint charly » where it saves a copy but still load the default name. Might be an option ? :)
>>>
>>> « Saves a copy » : do you mean you copy the full folder to another name ?
>>
>> I mean that when I « save as », I do it mainly because I know my next
>> code evaluation could crash the image ^^.
>>
>> So basically, what I need is to save a copy of the image (timestamped
>> eventually) but still using the original one. **So later, in case of
>> crash, I can roll back to a previous backup**.
>>
>> That is far easier to implement I guess than the tree and that would be
>> **very** useful to me at least ;-)
>>
>>
>>
>> Not sure, but I also think we should enforce by default to share the
>> iceberg repo. For most people, top save sandwich, etc, it seems a
>> better direction to me. This is optional right now but can’t we change
>> the default ?
>>
>>
>> Cheers,
>>
>> Cédrick
>>
>>
>>>
>>> Cheers,
>>> Christophe
>>
>>
>>
>