<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Dave.<div><br></div><div>Sounds very interesting! Please share. :-)</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 15.04.2020 01:37:10 schrieb David T. Lewis <lewis@mail.msen.com>:</p><div style="font-family:Arial,Helvetica,sans-serif">An MC update stream, such as the Squeak trunk update stream, relies<br>on a sequence of update maps stored in a repository. The update maps<br>(MCM files) do not retain information about their authors or the time<br>and reason for committing the maps, and they do not retain change<br>information if an existing update map is modified, as occasionally<br>may be required to correct a problem in the update stream.<br><br>I have found a way to extend the MCM configurations such that they<br>can be stored in a format that saves the additional version information,<br>and that is still readable by any earlier Squeak image. Updated images<br>can read and understand the version information, and will store new MCM<br>updates with comments, author initials, time stamps, and version history.<br><br>I have a working version of this in my own image. It seems to work quite<br>well, although I think I need to spend some more time using it before<br>suggesting it for general use. If there is in interest, I can put a copy<br>in the inbox.<br><br>Dave<br><br><br></div></blockquote>
</div></body>