<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Tim’s repo is using "status checks” and not only protected branch.</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Jul 19, 2016, at 5:01 PM, Renato Golin <<a href="mailto:renato.golin@linaro.org" class="">renato.golin@linaro.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p dir="ltr" class="">Can you show on Tim's repo how that won't work? </p><p dir="ltr" class="">Cheers, <br class="">
Renato </p>
<div class="gmail_extra"><br class=""><div class="gmail_quote">On 20 Jul 2016 12:59 a.m., "Mehdi Amini" <<a href="mailto:mehdi.amini@apple.com" class="">mehdi.amini@apple.com</a>> wrote:<br type="attribution" class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jul 19, 2016, at 4:44 PM, Renato Golin via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class=""><div class=""><p dir="ltr" class="">That is what I'm proposing, and Tim is helping us test. We should reach a solution quickly, and once we do, I'll update the document. </p></div></blockquote><div class=""><br class=""></div><div class="">Protected branch *alone* don’t enforce a linear history without the "status checks” feature. I don’t believe Chandler is proposing to use "status checks”, and he is concerned with “rewriting the history” more than enforcing a linear history, so you’ll have to be careful about what is the promise exactly. </div><div class=""><br class=""></div><div class="">— </div><div class="">Mehdi</div><div class=""><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><p dir="ltr" class="">Feel free to try his repo, I'll only try tomorrow. If you guys come up with a clear flow before that, let me know. </p><p dir="ltr" class="">Cheers, <br class="">
Renato </p>
<div class="gmail_extra"><br class=""><div class="gmail_quote">On 20 Jul 2016 12:36 a.m., "Chandler Carruth" <<a href="mailto:chandlerc@google.com" target="_blank" class="">chandlerc@google.com</a>> wrote:<br type="attribution" class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">I've not read all of the github threads, so sorry if this has been brought up, but...<br class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Tue, Jul 19, 2016 at 1:27 PM Renato Golin via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> 1. Pre-commit hooks, avoiding forced pushes / re-order<br class="">
<br class="">
GitHub doesn't support server hooks due to security concerns.<br class=""></blockquote><div class=""><br class=""></div><div class="">GitHub does support protected branches which prevent forced pushes. I've even played with them in the llvm GitHub project and they work as expected. It should give the exact workflow that I think LLVM devs are used to with Subversion of post-commit review.</div><div class=""><br class=""></div><div class="">-Chandler</div></div></div>
</blockquote></div></div>
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a><br class=""><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class=""></div></blockquote></div><br class=""></div></blockquote></div></div>
</div></blockquote></div><br class=""></body></html>