<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 9, 2014 at 1:27 PM, tim Rowledge <span dir="ltr"><<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>></span> wrote:<br>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"> <span style="color:rgb(34,34,34)">It may be that Chris’s technique for dumping the ancestry was less than perfect, but I’d say the real problem would likely be the ancestry code. Is there any plausible reason for a ‘clean’ image to have 9000 version-doohickeys taking up a couple of MB?</span></div>
</div>
<div class=""></div></blockquote></div><br></div><div class="gmail_extra">Sure. It's the same reason we ship 40MB of sources/changes files, rather than condensing sources frequently. This the revision history of the code in the image, and the fact that it's already there with no effort makes it easier to contribute to Squeak. That's helpful to newbies, and convenient for experienced developers. </div>
<div class="gmail_extra"><br></div><div class="gmail_extra">It wouldn't be that hard to come up with a scheme for shipping the version history separately and loading it when needed, but nobody has found that important.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Colin</div></div>