Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XeepS-0006sW-HF for bitcoin-development@lists.sourceforge.net; Thu, 16 Oct 2014 06:46:30 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of dashjr.org designates 192.3.11.21 as permitted sender) client-ip=192.3.11.21; envelope-from=luke@dashjr.org; helo=zinan.dashjr.org; Received: from zinan.dashjr.org ([192.3.11.21]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1XeepR-0003pd-Gn for bitcoin-development@lists.sourceforge.net; Thu, 16 Oct 2014 06:46:30 +0000 Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:be5f:f4ff:febf:4f76]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id F3A651080213; Thu, 16 Oct 2014 06:46:23 +0000 (UTC) From: Luke Dashjr To: Wladimir Date: Thu, 16 Oct 2014 06:46:21 +0000 User-Agent: KMail/1.13.7 (Linux/3.15.5-gentoo; KDE/4.12.5; x86_64; ; ) References: <201410160436.52259.luke@dashjr.org> In-Reply-To: X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201410160646.22544.luke@dashjr.org> 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 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1XeepR-0003pd-Gn Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Proposed BIP status changes 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, 16 Oct 2014 06:46:30 -0000 On Thursday, October 16, 2014 6:22:04 AM Wladimir wrote: > > Shouldn't we be doing this in a GitHub PR rather than spamming up the ML? > > Not really. BIP changes should be discussed on the mailing list, > that's the way to get community consensus (as specified in BIP1). > > Wladimir Discussion vs simple ACKing.