<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Jun 26, 2015 at 4:31 AM, Burton, Ross <span dir="ltr"><<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>></span> wrote:<br><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"><span class=""><br><div class="gmail_quote">On 26 June 2015 at 05:16, Jon Szymaniak <span dir="ltr"><<a href="mailto:jon.szymaniak@gmail.com" target="_blank">jon.szymaniak@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="overflow:hidden">GitHub provides this ability to download repository contents at<br>
a specified changeset as a zip file. This is generally *much* quicker<br>
than fetching the entire git repository.</div></blockquote></div><br></span>Github also can and will regenerate these tarballs whenever it feels like it, so you'll need to periodically update the checksums. Obviously as existing developers will tend to have the tarballs cached locally, it can be a while before this failure is reported back.</div><div class="gmail_extra"><br></div><div class="gmail_extra">A better solution might be to add support for "depth" to the git fetcher, so you can grab just the commit you are interested in instead of the entire repository. </div><span class="HOEnZb"><font color="#888888"><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></font></span></div>
</blockquote></div><br></div><div class="gmail_extra">Hi Ross,<br><br></div><div class="gmail_extra">Excellent point about the regeneration potentially yielding different checksums. I suppose they could change the compression level they use at any moment in time... I'll look into adding that depth support to the fetcher, as that doesn't look too hard at all.<br><br></div><div class="gmail_extra">I'm open to other suggestions as well, as this was just a first stab at it. I've been seeing that cloning this git repo containing binary firmware blobs takes an absurd amount of time, if it even finishes at all successfully.<br><br></div><div class="gmail_extra"></div><div class="gmail_extra">Cheers,<br></div><div class="gmail_extra">Jon<br></div></div>