[llvm-dev] [RFC] GitHub Survey - Please review
Chris Bieneman via llvm-dev
llvm-dev at lists.llvm.org
Fri Aug 19 10:06:29 PDT 2016
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.
A few questions I think would be useful.
(1) Which project(s) do you contribute to?
(2) Which project(s) do you regularly use?
(3) How often do you bisect LLVM with one or more subproject?
(4) Do you use any of the llvm.org <http://llvm.org/> projects without LLVM or with out-of-sync LLVM (i.e. trunk libunwind with an old LLVM)?
(5) In which ways do you get LLVM sources from LLVM.org <http://llvm.org/>?
(b) llvm.org <http://llvm.org/> Git mirrors
(d) GitHub Git mirrors
(6) Do you, or an organization you are affiliated with, maintain tooling or infrastructure that interacts with llvm.org <http://llvm.org/> and is not public?
> On Aug 19, 2016, at 5:57 AM, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> On 19 August 2016 at 13:50, Bruce Hoult <bruce at hoult.org> wrote:
>> For people who are doing read-only access, to include llvm in the build of
>> some other project, the impact might be as small as a one-time changing of
>> the URL for the "svn checkout" in their script.
> For that kind of use, I believe the GitHub SVN interface will "just
> work". I have tested it read-only and read-write access and my SVN
> client was very happy with it.
> Some people said it was a bit slow, but that should only make a
> difference if you're checking out the whole thing. (svn relocate may
> help, too).
> But there's also the idea of changing the process to Git, which would
> involve some changes to their scripts, but not a big one.
> I'm more worried with huge build systems that heavily use SVN as a
> core part of their infrastructure, making it a lot harder to "move to
> I'm expecting this number to be small nowadays...
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev