Re: [lldb-dev] [Release-testers] [8.0.0 Release] The final tag is in
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 via Release-testers wrote: > > 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-18.04.tar.xz > > > On Mon, Mar 18, 2019 at 8:04 AM Hans Wennborg via Release-testers > wrote: >> >> Dear testers, >> >> 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. >> >> Apologies for being behind schedule. It took longer than planned this time. >> >> Please build the final binaries and upload to the sftp. >> >> For those following along: this means 8.0.0 is done, but it will take >> a few days to get all the tarballs ready and published on the release >> web page. I will send the announcement once everything is ready. >> >> Thanks again everyone for your help with testing the release! >> >> Hans >> ___ >> Release-testers mailing list >> release-test...@lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > > > > -- > -Brian > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] [GitHub] RFC: Enforcing no merge commit policy
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 more likely that they will give an option that disables the merge button in PRs. It is already possible to prevent direct pushes to master by anyone, so this would be a very small change (literally disabling one button in the UI). David ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] [GitHub] RFC: Enforcing no merge commit policy
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) to run arbitrary post-receive hooks. What about a single, simple, specific post-receive hook that has been vetted by the github team, and that cannot by changed from the LLVM side without going through their customer support team (and additional vetting)? ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [llvm-dev] [cfe-dev] [GitHub] RFC: Enforcing no merge commit policy
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. >> >> It is quite unlikely that GitHub will allow LLVM (or any other project) to >> run arbitrary post-receive hooks. > > What about a single, simple, specific post-receive hook that has been vetted > by the github team, and that cannot by changed from the LLVM side without > going through their customer support team (and additional vetting)? GitHub already has something like this, called branch protections[1]. There just isn't a 'no merge commit' protection, but this is something I'm going to request. -Tom [1] https://help.github.com/en/articles/configuring-protected-branches > ___ > LLVM Developers mailing list > llvm-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
