[llvm-dev] [cfe-dev] [lldb-dev] GitHub anyone?
Mehdi Amini via llvm-dev
llvm-dev at lists.llvm.org
Fri Jun 3 11:04:33 PDT 2016
> On Jun 3, 2016, at 6:46 AM, Craig, Ben via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>> No matter what, once you push your branch and make it public, anyone
>> could pull it and then rewriting history gets trickier. IME it's best
>> to avoid doing that as much as possible.
> If we have automation that looks at public topic branches (possibly because of a github pull request), then people will start making branches public sooner rather than later. That's when we start getting into fixup territory.
We're getting off-track, but about this particular point we don't need to allow public branch in the official repository for that (I hope we won't allow it). For the purpose of testing private changes, there is always the possibility of opening a pull-request from a private fork.
> If we don't put any of that automation in place, and we only run tests post-commit, then yeah, I think that keeping changes private as long as possible is probably best.
> Employee of Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
More information about the llvm-dev