<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi Juan, Chapter updated accordingly, I left out the details you described bellow, though. <a class="moz-txt-link-freetext" href="https://cuis-smalltalk.github.io/TheCuisBook/Code-Management.html">https://cuis-smalltalk.github.io/TheCuisBook/Code-Management.html</a> <div class="moz-cite-prefix">Le 10/12/2020 à 17:06, Juan Vuletich a écrit : </div> <blockquote type="cite" cite="mid:5FD2478D.5040905@jvuletich.org">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. </blockquote> <pre class="moz-signature" cols="72">-- GNU Dr. Geo <a class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a> <a class="moz-txt-link-freetext" href="https://pouet.chapril.org/@hilaire">https://pouet.chapril.org/@hilaire</a></pre> </body> </html>