From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z5cD7-0002lz-LX for bitcoin-development@lists.sourceforge.net; Thu, 18 Jun 2015 15:58:37 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.169 as permitted sender) client-ip=209.85.223.169; envelope-from=gmaxwell@gmail.com; helo=mail-ie0-f169.google.com; Received: from mail-ie0-f169.google.com ([209.85.223.169]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z5cD6-0005pj-Q4 for bitcoin-development@lists.sourceforge.net; Thu, 18 Jun 2015 15:58:37 +0000 Received: by iebmu5 with SMTP id mu5so57660773ieb.1 for ; Thu, 18 Jun 2015 08:58:31 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.28.43 with SMTP id y11mr14250760igg.8.1434643111496; Thu, 18 Jun 2015 08:58:31 -0700 (PDT) Received: by 10.107.147.213 with HTTP; Thu, 18 Jun 2015 08:58:31 -0700 (PDT) In-Reply-To: References: <55828737.6000007@riseup.net> <20150618111407.GA6690@amethyst.visucore.com> <20150618114757.GB6690@amethyst.visucore.com> Date: Thu, 18 Jun 2015 15:58:31 +0000 Message-ID: From: Gregory Maxwell To: Mike Hearn Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gmaxwell[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Z5cD6-0005pj-Q4 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jun 2015 15:58:37 -0000 On Thu, Jun 18, 2015 at 1:36 PM, Mike Hearn wrote: >> And allegations that the project is "run like wikipedia" or "an edit war" >> are verifyably untrue. >> Check the commit history. > > This was a reference to a post by Gregory on Reddit where he said if Gavin > were to do a pull request for the block size change and then merge it, he > would revert it. And I fully believe he would do so! http://www.reddit.com/r/Bitcoin/comments/37pv74/gavin_andresen_moves_ahead_with_push_for_bigger/croxw9o?context=1 This is the only reddit comment I've made using the word revert in recent memory, so I know you couldn't be referring to another. >> I was recently in a situation similar to what Gavin is in insofar as a design dispute that could improperly solved by a git push. I'm pretty impressed he hasn't given in and done a midnight push. It's cool to see him back channeling support. > Such a change would be immediately reverted. And, I probably should have continued "and resulted with an immediate revocation of commit rights on the assumption that his account had been compromised." There is nothing controversial about that.