<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 26, 2015, at 7:47 AM, Burton, Ross <<a href="mailto:ross.burton@intel.com" class="">ross.burton@intel.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On 3 June 2015 at 22:21, Khem Raj <span dir="ltr" class=""><<a href="mailto:raj.khem@gmail.com" target="_blank" class="">raj.khem@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Can you explain why? The revision looks like 0.16.0 release.<br class="">
<br class="">
</span>its easy to develop libinput and prepare/test upstream patches since all upstreams want the patches against their latest master and its easy to switch to AUTOREV locally and do it.</blockquote><div class=""><br class=""></div><div class="">That's not a great reason and I'm against using git fetches when there's perfectly good tarballs available.</div><div class=""><br class=""></div></div></div></div></div></blockquote><div><br class=""></div><div>From a system integrators point of view, I agree with your sentiments. From a developers point of view not so much. We already have many recipes already fetching from git and more and more switching to use it see qt5 lately, there are perfectly fine tarballs released for QT5 too, just because its simpler to developer and integrate packages.</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class="">Ross </div></div></div></div>
</div></blockquote></div><br class=""></body></html>