___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Hi,
I would like to follow up on the previous thread[1], where there was a consensus
to disallow merge commits in the llvm github repository, and start a discussion
about how we should enforce this policy.
Unfortunately, GitHub does not provide a convenient way to fully enforce this
policy.
We c
I think we definitely will want to support github PRs, at the very least as
an _option_, even if we continue running/preferring phabricator.
Github PRs are how everyone who is not already super-involved in the llvm
project is going to want to contribute changes, and we ought to be as
welcoming as
Honestly I'm looking forward to GitHub's interface here.
On Tue, Mar 19, 2019, 1:25 PM James Y Knight via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> I think we definitely will want to support github PRs, at the very least
> as an _option_, even if we continue running/preferring phabricator.
>
>
On 18 Mar 2019, at 14:04, Hans Wennborg via Release-testers
wrote:
> The final version of 8.0.0 was just tagged from the release_80 branch
> at r356364. It's identical to rc5 except for a few documentation
> changes.
Again, I had to disable compiler-rt for this test run, as most of the
sanitize
> Github PRs are how everyone who is not already super-involved in the llvm
> project is going to want to contribute changes, and we ought to be as
> welcoming as possible to such users.
Still we'd need some policy & checks here. Say, what if someone will
issue a PR to LLVM 4.0 branch? With clear
