<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 29, 2014 at 1:51 PM, Eliot Miranda <span dir="ltr"><<a href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</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 dir="ltr">IMO, there's another thing worth doing, and that is sorting and uniqueifying the history. I see duplicate entries in the ancestry which causes it to bloat (I suspect this happens on e.g. merge, but I'm not sure). I have seen my manual attempts at uniqueifying ancestry shrink significantly the size of mcz files.</div>
</blockquote><div><br></div><div>We could may be uses Chris' unique registry idea to have canonical instances of VersionInfo. That would save memory in the image. We could also change the mcz format to allow references between nodes in the ancestry tree so that there's no duplicate information there. That would save space inside mcz files. </div>
<div><br></div><div>But the tree structure contains important information, and collapsing the tree into a linear history would prevent MC from doing merges properly.</div><div><br></div><div>Colin</div></div></div></div>