<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 Sep 4, 2016, at 9:34 AM, Patrice Kouame <<a href="mailto:pkouame@mac.com" class="">pkouame@mac.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">Ok Mehdi.</div><div class=""><br class=""></div><div class="">I'm obviously coming into this pretty late, but from a totally neutral user perspective having</div><div class="">recently rebuilt llvm and it's components on macOS Sierra. I think I am interpreting mono versus</div><div class="">multi repo correctly as "single repository for all llvm components/modules" vs. "multiple</div><div class="">(separate) repositories". So here's a humble perspective from an outsider: while building</div><div class="">all of the components separately was a slight (very) inconvenience adding a few more terminal</div><div class="">commands to my workflow, it did force me to RTFM and digest the project's architecture and</div><div class="">framework. In the end, I have a much better understanding of how all this connects.</div><div class="">Again, the impact on day to day development and maintenance is best left to you guys and </div><div class="">gals, but retaining a multiple logical delineation between modules works for me.</div></div></div></blockquote><div><br class=""></div><div><br class=""></div>Thanks for sharing your thoughts and experience!</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div class=""><br class=""></div><div class="">Has the move to native git/github been formally approved yet? I use Sourcetree, moving away from git svn would be a plus…</div></div></div></blockquote><div><br class=""></div><div>No, we’re still formalizing the proposals, then a survey will be sent out, then we’ll probably discuss this at the next llvm-dev meeting, then I don’t know :)</div><div><br class=""></div><div><br class=""></div><div>—</div><div>Mehdi</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div class=""><br class=""></div><div class="">It's all good.</div><div class=""><br class=""></div><div class="">Regards - Patrice Kouame</div><div class=""><br class=""></div><div class="">Sent from my iPad</div><div class=""><br class="">On Sep 3, 2016, at 10:59 PM, Mehdi Amini <<a href="mailto:mehdi.amini@apple.com" class="">mehdi.amini@apple.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Sep 3, 2016, at 6:05 PM, Patrice Kouame <<a href="mailto:pkouame@mac.com" class="">pkouame@mac.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">Someone mentioned llvm in a mono repository below…</div></div></div></blockquote><div class=""><br class=""></div><div class="">Right, we actually have a proposal to take what is in the current SVN repo here: <a href="http://llvm.org/svn/llvm-project/" class="">http://llvm.org/svn/llvm-project/</a> and migrate this to a single repository.</div><div class="">I was not sure if you were referring to this proposal (monorepo) or to the recent emails about “external libraries” that GCC uses like gmp and mpfr. </div><div class=""><br class=""></div><div class="">You can find more details here: <a href="https://reviews.llvm.org/D24167" class="">https://reviews.llvm.org/D24167</a></div><div class=""><br class=""></div><div class="">If you have some good reasons why you would think a proposal would be problematic to you, or one would better fit your workflow, feel free to expose them now.</div><div class=""><br class=""></div><div class="">Best,</div><div class=""><br class=""></div><div class="">— </div><div class="">Mehdi</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div class=""><br class="">On Sep 3, 2016, at 7:37 PM, Mehdi Amini <<a href="mailto:mehdi.amini@apple.com" class="">mehdi.amini@apple.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div class=""><div style="direction: inherit;" class=""><br class=""></div></div><div class=""><br class="">On Sep 3, 2016, at 3:04 PM, Patrice Kouame <<a href="mailto:pkouame@mac.com" class="">pkouame@mac.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><span class=""></span><br class=""><span class="">+1 for keeping it separate. </span><br class=""></div></blockquote><div style="direction: inherit;" class=""><br class=""></div><div style="direction: inherit;" class="">Can you clarify what you referring to specifically?</div><div style="direction: inherit;" class="">This sub thread (the last 4 messages) started with a mention of GCC dependencies. It is not clear to me how to relate to llvm now.</div><div style="direction: inherit;" class=""><br class=""></div><div style="direction: inherit;" class="">Mehdi</div><div style="direction: inherit;" class=""><br class=""></div><blockquote type="cite" class=""><div class=""><span class=""></span><br class=""><span class="">One can easily set up a git subproject structure if the need is pressing...</span><br class=""><span class=""></span><br class=""><span class="">Patrice</span><br class=""><span class=""></span><br class=""><blockquote type="cite" class=""><span class="">On Sep 3, 2016, at 5:39 PM, Mehdi Amini via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">On Sep 2, 2016, at 12:33 PM, Dimitry Andric via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">On 16 Aug 2016, at 00:12, Lawrence, Peter via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">As someone that has worked with both gcc and llvm,</span><br class=""></blockquote></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">One thing about gcc that drives me bat-guano-crazy is that</span><br class=""></blockquote></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">First you check out gcc, try to build it, and find that you also</span><br class=""></blockquote></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">Need mpc, so you check that out and try to build it, and</span><br class=""></blockquote></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">Find out you also need gmp, so you check that out and try</span><br class=""></blockquote></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">To build it, and find out that you also need mpfr, …..</span><br class=""></blockquote></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">I can understand your frustration, but these are all completely external libraries, and it does not really make sense to include this into any mono-repository.</span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">For example, you are also dependent on libc headers, are you going to include these into your repository? And kernel headers? The end result will possibly include half of GitHub into that mono-repository... :)</span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">So as usual, for any open source project, read the requirements first, and install those from whatever your local package management system is.</span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="">If LLVM is going to use a mono-repository, it should only include LLVM components, in my opinion.</span><br class=""></blockquote></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class="">This seems a good principle in general, but note that we already included external projects in the repo. Out-of-my-head right now I can think of the google tests library, and ISL.</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class="">— </span><br class=""></blockquote><blockquote type="cite" class=""><span class="">Mehdi</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class="">_______________________________________________</span><br class=""></blockquote><blockquote type="cite" class=""><span class="">LLVM Developers mailing list</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a></span><br class=""></blockquote><blockquote type="cite" class=""><span class=""><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a></span><br class=""></blockquote></div></blockquote></div></blockquote></div></div></blockquote></div><br class=""></div></blockquote></div></div></blockquote></div><br class=""></body></html>