Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <milly@bitcoins.info>) id 1Z5bCJ-0001Rh-B1
	for bitcoin-development@lists.sourceforge.net;
	Thu, 18 Jun 2015 14:53:43 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitcoins.info
	designates 70.90.2.18 as permitted sender) client-ip=70.90.2.18;
	envelope-from=milly@bitcoins.info; helo=mail.help.org; 
Received: from mail.help.org ([70.90.2.18])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.76) id 1Z5bCH-0003YE-BV
	for bitcoin-development@lists.sourceforge.net;
	Thu, 18 Jun 2015 14:53:43 +0000
Received: from [10.1.10.25] (B [10.1.10.25]) by mail.help.org with ESMTPA
	; Thu, 18 Jun 2015 10:53:33 -0400
Message-ID: <5582DB62.8000700@bitcoins.info>
Date: Thu, 18 Jun 2015 10:53:22 -0400
From: Milly Bitcoin <milly@bitcoins.info>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
	rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
References: <55828737.6000007@riseup.net>	<CANEZrP3M7+BsZKLFZV-0A_fC7NmMGbTDxsx3ywru3dSW78ZskQ@mail.gmail.com>	<20150618111407.GA6690@amethyst.visucore.com>	<CAPg+sBj_go==m6-++sA53imYdz4OLH4bkyiuAyEM8YR8CaTd=w@mail.gmail.com>	<CANEZrP04SUHShoqUkA3aSs3yEP3GSsZ_3ZOGFXyJfNve5KTPfA@mail.gmail.com>
	<20150618140544.GA7674@amethyst.visucore.com>
In-Reply-To: <20150618140544.GA7674@amethyst.visucore.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.5 (-)
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 SPF_PASS               SPF: sender matches SPF record
X-Headers-End: 1Z5bCH-0003YE-BV
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 18 Jun 2015 14:53:43 -0000

 >So I'm *not* the decider for anything that concerns the behavior of 
the global consensus, and I cannot be, as I have explained in the 
previous post.

The person who decides if a pull request is accepted is a decider and 
significantly affects the behavior of the global consensus.  The only 
option for someone who doesn't agree is to hard fork.  There is no way 
around that and you should just accept that fact and move on.

Russ