Hi, ohh ... sorry - I did not notice that it was commited that way. The commit window showed the inteded change on removing only the unused temp var in #newCString: as the only change. I can confirm: also the SqueakSource changeset mechanism http://www.squeaksource.com/Alien/changes/Alien-TorstenBergmann.41(RonieSalg... reveals that it changed much more than intended. Reason is also found: I used Pharo 7 for the commit as I fixed it there and as Pharo 7 image is now changed to be bootstrapped and based on our new friend "git" this unfortunately committed in Monticello without the author/timestamp. I repaired and fixed it in a new 42 version for Alien on SqueakSource, rebasing on the previous one from Ronie again: Name: Alien-TorstenBergmann.42 Author: TorstenBergmann Time: 8 January 2018, 7:52:42.082522 pm UUID: 42030335-3a5b-ad49-99e7-54889fc57194 Ancestors: Alien-RonieSalgado.40 - remove unused var in #newCString: - rebased on Alien-RonieSalgado.40.mcz   Sorry for any inconvenience this may have caused you. Bye T.   Gesendet: Montag, 08. Januar 2018 um 03:37 Uhr Von: "Eliot Miranda" <eliot.miranda@gmail.com> An: "Squeak Virtual Machine Development Discussion" <vm-dev@lists.squeakfoundation.org> Cc: "Discusses Development of Pharo" <pharo-dev@lists.pharo.org> Betreff: Re: [Pharo-dev] [Vm-dev] Alien-TorstenBergmann.41 wipes all method stamps     On Sun, Jan 7, 2018 at 6:05 PM, David T. Lewis <lewis@mail.msen.com[mailto:lewis@mail.msen.com]> wrote: Alien-TorstenBergmann.41 is in repository Alien on squeaksource, and was intended to be a minor update. But it clobbers all method stamps in the entire package. Could whoever saved this update please check this, and maybe re-save it with just Torsten's intended Alien class>>newCString: fix?   And can someone please explain what was the cause of the wiped method stamps?   _,,,^..^,,,_ best, Eliot