<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 30, 2014 at 9:25 AM, Colin Putney <span dir="ltr"><<a href="mailto:colin@wiresong.com" target="_blank">colin@wiresong.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"><div class="gmail_extra"><div class="gmail_quote"><div>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></div></div></div></div></blockquote></div><br></div><div class="gmail_extra">I should have checked on this before posting. :-)</div><div class="gmail_extra"><br></div><div class="gmail_extra">It turns out we already do this, so optimizing the ancestry data in an mcz file would require a pretty radical change.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Colin</div></div>