<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="">I think that if we’re going to do a survey we should gather more information about how people interact with the LLVM projects, not just opinions on the proposals.<div class=""><br class=""></div><div class="">A few questions I think would be useful.</div><div class=""><br class=""></div><div class="">(1) Which project(s) do you contribute to?</div><div class="">(2) Which project(s) do you regularly use?</div><div class="">(3) How often do you bisect LLVM with one or more subproject?</div><div class="">(4) Do you use any of the <a href="http://llvm.org" class="">llvm.org</a> projects without LLVM or with out-of-sync LLVM (i.e. trunk libunwind with an old LLVM)?</div><div class="">(5) In which ways do you get LLVM sources from <a href="http://llvm.org" class="">LLVM.org</a>?</div><div class=""> (a) SVN</div><div class=""> (b) <a href="http://llvm.org" class="">llvm.org</a> Git mirrors</div><div class=""> (c) Git-SVN</div><div class=""> (d) GitHub Git mirrors</div><div class=""> (e) Other</div><div class="">(6) Do you, or an organization you are affiliated with, maintain tooling or infrastructure that interacts with <a href="http://llvm.org" class="">llvm.org</a> and is not public?</div><div class=""><br class=""></div><div class="">-Chris</div><div class=""><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 19, 2016, at 5:57 AM, Renato Golin 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 class="">On 19 August 2016 at 13:50, Bruce Hoult <<a href="mailto:bruce@hoult.org" class="">bruce@hoult.org</a>> wrote:<br class=""><blockquote type="cite" class="">For people who are doing read-only access, to include llvm in the build of<br class="">some other project, the impact might be as small as a one-time changing of<br class="">the URL for the "svn checkout" in their script.<br class=""></blockquote><br class="">For that kind of use, I believe the GitHub SVN interface will "just<br class="">work". I have tested it read-only and read-write access and my SVN<br class="">client was very happy with it.<br class=""><br class="">Some people said it was a bit slow, but that should only make a<br class="">difference if you're checking out the whole thing. (svn relocate may<br class="">help, too).<br class=""><br class="">But there's also the idea of changing the process to Git, which would<br class="">involve some changes to their scripts, but not a big one.<br class=""><br class="">I'm more worried with huge build systems that heavily use SVN as a<br class="">core part of their infrastructure, making it a lot harder to "move to<br class="">git".<br class=""><br class="">I'm expecting this number to be small nowadays...<br class=""><br class="">cheers,<br class="">--renato<br class="">_______________________________________________<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></div></blockquote></div><br class=""></div></div></body></html>