[llvm-dev] [cfe-dev] [lldb-dev] GitHub anyone?
Rafael Espíndola via llvm-dev
llvm-dev at lists.llvm.org
Tue Jun 21 07:32:32 PDT 2016
For what it is worth, I fully support *any* change that moves us away
from having our own infrastructure. We should really stop hosting our
own code repositories, databases and mailing lists.
For that, I support the proposal to move to github, but would also
support moving to another hosting service.
On 10 June 2016 at 14:25, Tim Northover via cfe-dev
<cfe-dev at lists.llvm.org> wrote:
> On 2 June 2016 at 08:48, Renato Golin via lldb-dev
> <lldb-dev at lists.llvm.org> wrote:
>> Of all those issues, Windows tooling is a minor problem that shouldn't
>> impact decision that much and sub-modules need a lot of ironing out to
>> be considered good enough. My *personal* take away is that sub-modules
>> (or an alternative server side solution) is the only strong technical
>> issue we need to solve before we decide.
> I think Takumi's repository and script covers the real uses
> (bisection, principally) as well as we need and probably better than
> SVN. I suppose we might extend it to put an auto-incrementing revision
> number in the commit message too, but that's trivial.
> I think the responses in the thread have been heavily in favour
> (including after AAron's mention in LLVM weekly), so we should either
> get a more rigorous survey going as Tanya suggested (if we think it's
> useful) or get started on the actual move.
> I'm not really convinced that a survey would reach enough of a wider
> audience to affect our actions here, though I think the results would
> be very interesting anyway in the longer term (particularly on
> preferred workflows).
>> How does a move look like?
>> If we decide to move, the proposed schedule is something like this:
>> STEP #1 : Pre Move
>> 1. Register an official GitHub project with the LLVM foundation.
> Chandler already did that: https://github.com/llvm. So we're one step
> in already!
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
More information about the llvm-dev