[LLVMdev] Howdy + GIT

[Reid Kleckner]

Hello again! :)

I just wanted to note that many of us are already using the official git
mirror at http://llvm.org/git/llvm.git and there are other unofficial git
mirrors on github. Chapuni even has an all-in-one LLVM git repo at
https://github.com/chapuni/llvm-project for easy git bisection.

While many people appreciate the local workflows that git enables, I think
as collaborators we appreciate the simple, strictly linear history model
that the upstream LLVM SVN repo enforces.

I also think the repository granularity is fine enough today. It is already
a challenge for me to keep LLVM, Clang, LLDB, LLD, compiler-rt, and libc++
in sync, and bisecting across them is hard.

In terms of better collaboration tools, I think my biggest pain points have
been:
- Bugzilla isn't the best issue tracker anymore
- Occasional downtime for llvm.org and mailing lists
- Buildbot mail is spammy and inaccurate, but github doesn't help much here
either

As far as code sharing/review tools go, I think Phabricator is doing a
pretty good job.

At the end of the day, I don't think my pain points add up to enough to
make it worth switching any infrastructure.

On Thu, Jan 15, 2015 at 10:13 AM, Reid Spencer <reid at reactific.com> wrote:

> Hello LLVMers,
>
> It has been a while (8 years?) since I’ve been involved with LLVM but I’m
> considering picking it up again. My recent review of the code base has led
> me to wonder if it isn’t time to update the code base, specifically:
>
>    - Convert to GIT
>    - Refactor into smaller, separate, reusable libraries
>    - Host the master repository at GitHub (amongst other places)
>
>
> My reasons for doing this don’t have to do with the code repository
> choice, but rather encouraging innovation. LLVM’s private and centralized
> repository is now hurting the project, I believe. The GIT model fosters
> better code sharing and GitHub in particular makes integration of new ideas
> significantly easier. It is my opinion that LLVM is missing out on
> contributions simply because it doesn’t utilize the modern cloud-based
> tools.
>
> So, what’s your (developer) response to this? “No way in hell”,
> “Interesting idea”, “We should do that”, or “Why haven’t we done it yet?”
>
> FYI: Yes, I’m signing up to do a bunch of the leg work if the development
> community wants this.  If not, I’ll make other plans.
>
> Sorry if this topic has been covered .. the archives are not searchable
> (google group, anyone?).
>
> Reid Spencer
>
>
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150115/021703e4/attachment.html>