[lldb-dev] LLVM 8.0.0 Release

2019-03-20 Thread Hans Wennborg via lldb-dev
I'm pleased to announce that LLVM 8 is now available. Get it here: https://llvm.org/releases/download.html#8.0.0 This release contains the work on trunk up to Subversion revision r351319, plus work on the release branch. It's the result of the LLVM community's work over the past six months, inclu

Re: [lldb-dev] [Release-testers] [8.0.0 Release] The final tag is in

2019-03-20 Thread Brian Cain via lldb-dev
Uploaded ubuntu and SLES tarballs: db0a5f7729507ddc4b161eff70cffcf5de052347 clang+llvm-8.0.0-x86_64-linux-sles11.3.tar.xz 2be69be355b012ae206dbc0ea7d84b831d77dc27 clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz 6aeb8aa0998d37be67d886b878f27de5e5ccc5e4 clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu

Re: [lldb-dev] [cfe-dev] [GitHub] RFC: Enforcing no merge commit policy

2019-03-20 Thread James Y Knight via lldb-dev
Then we should not accept it. What if someone did the same on a phabricator review? On Wed, Mar 20, 2019 at 2:39 AM Anton Korobeynikov wrote: > > 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 > we

Re: [lldb-dev] [llvm-dev] [GitHub] RFC: Enforcing no merge commit policy

2019-03-20 Thread David Greene via lldb-dev
Tom Stellard via llvm-dev writes: > 1. Have either a status check or use the "Rebase and Merge" policy for > pull requests to disallow merge commits. Disable direct pushes to the > master branch and update the git-llvm script to create a pull request > when a developer does `git llvm push` and t

Re: [lldb-dev] [GitHub] RFC: Enforcing no merge commit policy

2019-03-20 Thread Zachary Turner via lldb-dev
On Tue, Mar 19, 2019 at 12:00 PM Tom Stellard via lldb-dev < lldb-dev@lists.llvm.org> wrote: > 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 enforc

Re: [lldb-dev] [GitHub] RFC: Enforcing no merge commit policy

2019-03-20 Thread Tom Stellard via lldb-dev
On 03/20/2019 10:41 AM, Zachary Turner wrote: > > > On Tue, Mar 19, 2019 at 12:00 PM Tom Stellard via lldb-dev > mailto:lldb-dev@lists.llvm.org>> wrote: > > Hi, > > I would like to follow up on the previous thread[1], where there was a > consensus > to disallow merge commits in th

Re: [lldb-dev] [cfe-dev] [GitHub] RFC: Enforcing no merge commit policy

2019-03-20 Thread Zachary Turner via lldb-dev
It sounds like we need to get someone from the Foundation (chandlerc@, lattner@, tanya@, someone else?) to reach out to them offline about this. On Wed, Mar 20, 2019 at 11:23 AM Arthur O'Dwyer wrote: > On Wed, Mar 20, 2019 at 2:19 PM Tom Stellard via cfe-dev < > cfe-...@lists.llvm.org> wrote: >

Re: [lldb-dev] [cfe-dev] [GitHub] RFC: Enforcing no merge commit policy

2019-03-20 Thread Tom Stellard via lldb-dev
On 03/20/2019 11:38 AM, Zachary Turner wrote: > It sounds like we need to get someone from the Foundation (chandlerc@, > lattner@, tanya@, someone else?) to reach out to them offline about this. > Yes, we will try to reach out to GitHub directly about this, but I still think we need some kind of

Re: [lldb-dev] [cfe-dev] [GitHub] RFC: Enforcing no merge commit policy

2019-03-20 Thread Brian Cain via lldb-dev
On Tue, Mar 19, 2019 at 2:00 PM Tom Stellard via cfe-dev < cfe-...@lists.llvm.org> wrote: > 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 t