[Cuis-dev] Changes not recoverable
Hilaire Fernandes
hilaire at drgeo.eu
Thu Dec 10 11:52:57 PST 2020
Hi Juan,
Chapter updated accordingly, I left out the details you described
bellow, though.
https://cuis-smalltalk.github.io/TheCuisBook/Code-Management.html
Le 10/12/2020 à 17:06, Juan Vuletich a écrit :
> Hi Hilaire,
>
> The .changes file includes all the code that was loaded into the
> image. This (obviously) includes code for Cuis updates and any
> packages you install. This makes recovering changes by hand harder.
> But each time you start Cuis and make changes, another file is
> created, named, for example Cuis5.0-4426.user.changes. If the file
> already exists, it gets renamed. So, for each session, you get files
> Cuis5.0-4426.user.xxx.changes where xxx is a number, starting with
> 001. Those files don't include installed changesets or packages, just
> user entered code. And you have a file for each session. This makes
> recovery more convenient. I prefer them to the recovery tools based on
> the regular .changes file.
>
> Having these additional files for user changes made it possible to
> discard the modifications to the regular .changes file on image exit.
> As the image is not saved, these changes are not needed anymore. This
> prevents the .changes file to grow too much, and it also means that
> the .changes file is not marked dirty by Git.
>
> We'd rewrite the changes recovery tools to use the *.user.???.changes
> files instead.
--
GNU Dr. Geo
http://drgeo.eu
https://pouet.chapril.org/@hilaire
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20201210/611e325f/attachment.htm>
More information about the Cuis-dev
mailing list