<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 9, 2017, at 9:06 AM, Mehdi AMINI via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">2017-05-09 9:03 GMT-07:00 David Chisnall <span dir="ltr" class=""><<a href="mailto:David.Chisnall@cl.cam.ac.uk" target="_blank" class="">David.Chisnall@cl.cam.ac.uk</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 9 May 2017, at 16:59, Mehdi AMINI <<a href="mailto:joker.eph@gmail.com" class="">joker.eph@gmail.com</a>> wrote:<br class="">
><br class="">
> I'm not sure if you really read the last sentence of what I wrote, or if you followed the previous discussions on the plan here?<br class="">
> At this point I believe that this concern is non-existent per the read-only individual repo.<br class="">
<br class="">
</span>The read-only repo is only useful if you don’t intend to contribute stuff back upstream. </blockquote><div class=""><br class=""></div><div class="">Your point was about CI...</div><div class="">(unless you're working on some CI that would fix bugs and send PR?)</div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> There is no convenient workflow for cloning libunwind / libc++ / libwhatever, hacking on it, and sending pull requests.<br class=""></blockquote><div class=""><br class=""></div><div class="">We considered git-svn for this though.</div><div class=""><br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br class="">
> We can leave it there :)<br class="">
> There have been extensive discussions, a BoF, and documentations, please refer you to these first (granted we haven't really talked about libunwind, but I'm not sure many people will be strongly opposed to libunwind having its separate life).<br class="">
<br class="">
</span>There have been multiple discussions, and the conclusion from all that I have participated in was that projects that are tightly version locked to LLVM should be in the monorepo, everything else should be separate. Apparently there is now a plan underway to not do this and to make life harder for people who work on the projects that are not version locked to LLVM.<br class=""></blockquote><div class=""><br class=""></div><div class="">We have a different understanding.</div></div></div></div></div></blockquote><div><br class=""></div><div>I feel like I need to take a minute here to voice my supreme frustration with the way this discussion has gone and this small sentence captures it entirely.</div><div><br class=""></div><div>From beginning to end these git migration conversations have involved a whole lot of people talking past each other and a lot of assumptions that are not shared. Many of us are very much not on the same page. The only thing that we had a significant consensus on was that we'd like to move to GitHub. Other than that we have more disagreement than agreement.</div><div><br class=""></div><div>We do not have consensus on an all-in-one monorepo, and any notion that we do is ignoring the significant dissent. There was less disagreement with a mono-repo that had only tightly coupled projects, but that itself is hard to nail down and define, and there are still many people (myself included) who prefer the multi-repo solution.</div><div><br class=""></div><div>Mehdi, I don't know if it is your intent, but in many places in this thread you sound as if this decision has been made and the community is fully supporting your decision. Please don't do that. It would be nice if as a community we considered the concerns of our members instead of offhand dismissing them.</div><div><br class=""></div><div>I think we should spend some time discussing and understanding the needs of our corporate contributors and the needs of the other open source projects that contribute to, use, and distribute LLVM. I believe that disregarding the concerns of communities like the BSD and Linux communities would be a severe detriment to the LLVM project.</div><div><br class=""></div><div>-Chris</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""><br class=""></div><div class="">-- </div><div class="">Mehdi</div><div class=""><br class=""></div></div></div></div>
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></blockquote></div><br class=""></body></html>