[llvm-dev] RFC: Move the test-suite LLVM project to GitHub?
Chandler Carruth via llvm-dev
llvm-dev at lists.llvm.org
Wed Feb 24 23:16:16 PST 2016
On Wed, Feb 24, 2016 at 10:21 PM Pete Cooper via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Sent from my iPhone
> > On Feb 24, 2016, at 6:25 PM, Chandler Carruth via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
> > I just want to clarify in case anyone is confused: I am in no way
> suggesting that we would use pull requests, issues, or anything else as
> part of the workflow for the test suite. I'm fine if folks want to talk
> about that later, but I really view it as a separate discussion. I'm much
> more interested in just leveraging the managed *hosting* of the repository
> This is actually the discussion I really want to happen before we move any
> Firstly, I use git and git-svn every day so I would much prefer the test
> suite in git. So I'm still very much a +1 for that.
> However, when I first started using git for llvm I had to adjust from the
> svn commands to the git ones and using pull/rebase instead of things like
> Learning those things in my own repo is fine, and several times I screwed
> up and blew away the repo to start again from a good state. But the point
> is that I made those mistakes on my own machine. I'm scared of anyone else
> making those mistakes to the llvm test suite. That is the big advantage of
> the pull request model and I think that's something we should consider for
> any git based llvm code, including the tests.
> I'm also open to alternatives, but as I said, we need some way, even if
> it's pre-commit hooks, to make sure that anyone other that admins are
> behaving (not pushing too many commits at a time, no merges, etc)
Yep. I have no idea what the correct process is here.
If folks are generally happy about this direction, I'll try to have a
concrete proposal of a process. It will be *very* minimal so as to be safe
and match as closely as possible the existing workflows.
That said, this is yet again why I think the cost/benefit tradeoff is
better for the test suite. In the worst case, if we hose the repository for
the test suite, it is likely to be incredibly easier to fix as we won't
have 50 people all trying to get work done by landing patches at the same
time as thing go sideways. And if we lose some detail of history, as long
as we recover the essence, its a much less big deal.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev