From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 6F6718D7 for ; Wed, 19 Aug 2015 18:20:22 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail148110.authsmtp.com (outmail148110.authsmtp.com [62.13.148.110]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id A8AB716B for ; Wed, 19 Aug 2015 18:20:21 +0000 (UTC) Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237]) by punt16.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t7JIKGx1053200; Wed, 19 Aug 2015 19:20:16 +0100 (BST) Received: from muck (S0106e091f5827ad2.ok.shawcable.net [24.71.232.17]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t7JIKBKM092996 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 19 Aug 2015 19:20:14 +0100 (BST) Date: Wed, 19 Aug 2015 11:20:11 -0700 From: Peter Todd To: Btc Drak Message-ID: <20150819182010.GB12306@muck> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="7ZAtKRhVyVSsbBD2" Content-Disposition: inline In-Reply-To: X-Server-Quench: f053244e-469e-11e5-9f75-002590a135d3 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdwsUGUATAgsB AmMbWl1eUl17WGY7 aQ5PagRDYElMQQRt T01BRU1TWkFve2V6 dGVjUhBwfgxANnd5 Z0csCHBeX0Z+cRNg RkhdQHAHZDJldWlJ V0VFdwNWdQpKLx5G bwR8GhFYa3VsNCMk FAgyOXU9MCtqYA5U XgoKLFRacXpDMDkm RHjL X-Authentic-SMTP: 61633532353630.1024:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 24.71.232.17/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] Bitcoin XT Fork X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Aug 2015 18:20:22 -0000 --7ZAtKRhVyVSsbBD2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 19, 2015 at 06:32:14PM +0100, Btc Drak via bitcoin-dev wrote: > On Wed, Aug 19, 2015 at 5:53 PM, Adam Back via bitcoin-dev > wrote: > > ignored the warnings. Many also warned that 75% was an optimally BAD > > trigger ratio (and that in a hard fork it is not a miner vote really > > as in soft-forks). Gavin & Mike ignored that warning to. I know they > > heard those warnings because I told them 1:1 in person or via email > > and had on going conversations. Others did too. >=20 > I would like to add for the record, I also warned Gavin of this in his > PR to Bitcoin Core, and also suggested a timeout which if > activation/enforcement did not occur within, hard fork deployment > would be cancelled. His response was to delete these from the PR > claiming thresholds were not relevant conversation in his PR and > belonged elsewhere (even though they had already been discussed > elsewhere). Normal GitHub users submitting pull-reqs to Bitcoin Core can't delete other users' comments on their own pull-reqs... IMO that's an abuse of the pull-req process, and in turn, Gavin Andresens's commit access rights for the Bitcoin Core repo. That kind of comment is perfectly on topic in the pull-req review process; deleting it harms that process by removing useful information about the trade-offs of the pull-req, both for people now, as well as future efforts investigating the history of Bitcoin's protocol development. I think this should weigh in favor of Gavin Andresen not having commit privileges for the Bitcoin Core repository. --=20 'peter'[:-1]@petertodd.org 00000000000000000402fe6fb9ad613c93e12bddfc6ec02a2bd92f002050594d --7ZAtKRhVyVSsbBD2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iQGrBAEBCACVBQJV1MjYXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw MDAwMDAwMDAwMDAwMDAwNDAyZmU2ZmI5YWQ2MTNjOTNlMTJiZGRmYzZlYzAyYTJi ZDkyZjAwMjA1MDU5NGQvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0 ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udxkrQf7BiQ4RMO5/umlLmAvh3qix/wp ytooxIkGUpyBKuwPlf7GnZkUozEvblLsIrLxkSQMjqCc66rWi2u+VEUtTCT90yfO YJs086PjGLIpH83HdhSSiQSOHUcsAd0EECFitlDLLJYpA6n9mLVKXq65nEUdZqlP 5ABCKj46EDid90SeQrlKt/FuSuBrT7EaHYlMJPgkV1F4MjTAvdt+QJqVSBuk/ZPW Hr3pN5rpdhpoBeKHYCUmeUdY/BjSjw5KWA0191zoHtHZyXLzjvvB4AZeec8JQAAM R8uPRrBJo+6HCpFVEje1cHobzNwmHKp7fGZcgB8DhR2/Fi7bWOP81m7N58fCNQ== =ZSbq -----END PGP SIGNATURE----- --7ZAtKRhVyVSsbBD2--