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

2019-03-21 Thread Tom Stellard via lldb-dev
On 03/21/2019 10:32 AM, Pavel Labath via llvm-dev wrote: > On 21/03/2019 13:12, David Chisnall via lldb-dev wrote: >> On 20 Mar 2019, at 18:23, Arthur O'Dwyer via cfe-dev >> wrote: >>> >>> Server-side hooks are the answer to this problem. There is no problem. You >>> just use a server-side hook.

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

2019-03-21 Thread Pavel Labath via lldb-dev
On 21/03/2019 13:12, David Chisnall via lldb-dev wrote: On 20 Mar 2019, at 18:23, Arthur O'Dwyer via cfe-dev wrote: Server-side hooks are the answer to this problem. There is no problem. You just use a server-side hook. It is quite unlikely that GitHub will allow LLVM (or any other project

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

2019-03-21 Thread David Chisnall via lldb-dev
On 20 Mar 2019, at 18:23, Arthur O'Dwyer via cfe-dev wrote: > > Server-side hooks are the answer to this problem. There is no problem. You > just use a server-side hook. It is quite unlikely that GitHub will allow LLVM (or any other project) to run arbitrary post-receive hooks. It is far mor

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

2019-03-21 Thread Diana Picus via lldb-dev
Uploaded ARM & AArch64: 998e9ae6e89bd3f029ed031ad9355c8b43441302c0e17603cf1de8ee9939e5c9 clang+llvm-8.0.0-aarch64-linux-gnu.tar.xz ddcdc9df5c33b77740e4c27486905c44ecc3c4ec178094febeab60124deb0cc2 clang+llvm-8.0.0-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On Wed, 20 Mar 2019 at 14:39, Brian Cain