Le 04/02/2016 13:09, Henrik Johansen a écrit :
Also, the ancestry of all packages in Pharo Core was truncated a few years back, which also screwed up merging*. I don't think anyone looked into why it happened.
It was done on purpose for the Pharo 3 release to reduce the amount of memory used by the MCVersionInfo instances.
For Pharo 4, a lazy loading of the MCVersionInfo was implemented instead. We should have recreated the lost history then, but it seemed not to have been important.
Thierry
