summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBryan Bishop <kanzure@gmail.com>2015-05-07 09:18:17 -0500
committerbitcoindev <bitcoindev@gnusha.org>2015-05-07 14:18:26 +0000
commitd00e3969dd3d35d25c1d0eb859597980412d6119 (patch)
treedd8d2a42f65c30381a8ebd7b3a8b3ac136ab8561
parenta07bbab4736ac2f055242d274c324fd32fca3f9e (diff)
downloadpi-bitcoindev-d00e3969dd3d35d25c1d0eb859597980412d6119.tar.gz
pi-bitcoindev-d00e3969dd3d35d25c1d0eb859597980412d6119.zip
Re: [Bitcoin-development] Block Size Increase
-rw-r--r--9c/fccc2b4f397828e0ac4780c2a92eb8b4e8fad085
1 files changed, 85 insertions, 0 deletions
diff --git a/9c/fccc2b4f397828e0ac4780c2a92eb8b4e8fad0 b/9c/fccc2b4f397828e0ac4780c2a92eb8b4e8fad0
new file mode 100644
index 000000000..03932527b
--- /dev/null
+++ b/9c/fccc2b4f397828e0ac4780c2a92eb8b4e8fad0
@@ -0,0 +1,85 @@
+Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
+ helo=mx.sourceforge.net)
+ by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <kanzure@gmail.com>) id 1YqMd8-0003co-CN
+ for bitcoin-development@lists.sourceforge.net;
+ Thu, 07 May 2015 14:18:26 +0000
+Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
+ designates 209.85.217.176 as permitted sender)
+ client-ip=209.85.217.176; envelope-from=kanzure@gmail.com;
+ helo=mail-lb0-f176.google.com;
+Received: from mail-lb0-f176.google.com ([209.85.217.176])
+ by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
+ (Exim 4.76) id 1YqMd6-0003EK-Fb
+ for bitcoin-development@lists.sourceforge.net;
+ Thu, 07 May 2015 14:18:26 +0000
+Received: by lbbqq2 with SMTP id qq2so32077703lbb.3
+ for <bitcoin-development@lists.sourceforge.net>;
+ Thu, 07 May 2015 07:18:18 -0700 (PDT)
+MIME-Version: 1.0
+X-Received: by 10.112.17.68 with SMTP id m4mr3349231lbd.10.1431008298114; Thu,
+ 07 May 2015 07:18:18 -0700 (PDT)
+Received: by 10.152.18.168 with HTTP; Thu, 7 May 2015 07:18:17 -0700 (PDT)
+In-Reply-To: <CANEZrP1CU0kB0vXeXUX1L8byaT-Zf2xg+3N+GeNthi_i6bn1qw@mail.gmail.com>
+References: <554A91BE.6060105@bluematt.me>
+ <CANEZrP3wGWHdz+ut6pvke5TJJsc1rTFt8sn2KziX35oL5LAsyg@mail.gmail.com>
+ <CABm2gDpDvk2VsQ+mJ-BoeBKmvu9jBXNujZEFKuCStRNjFL6VOA@mail.gmail.com>
+ <CANEZrP2zAGCCBhNa4=9yw+A_Dn5o4SQXoPTE_qcJzZ1dFuF2tw@mail.gmail.com>
+ <CABm2gDqd6iHRUDKZWWTudcC1QkYa+rCuHjz7pMC2K1Db8wpgfA@mail.gmail.com>
+ <CANEZrP1CU0kB0vXeXUX1L8byaT-Zf2xg+3N+GeNthi_i6bn1qw@mail.gmail.com>
+Date: Thu, 7 May 2015 09:18:17 -0500
+Message-ID: <CABaSBaxP2VGcH4gugZgr=t35NGSTF7QPPdQnYOo3osMg3J5tGg@mail.gmail.com>
+From: Bryan Bishop <kanzure@gmail.com>
+To: Mike Hearn <mike@plan99.net>, Bryan Bishop <kanzure@gmail.com>
+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
+ (kanzure[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: 1YqMd6-0003EK-Fb
+Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
+Subject: Re: [Bitcoin-development] Block Size Increase
+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, 07 May 2015 14:18:26 -0000
+
+On Thu, May 7, 2015 at 9:05 AM, Mike Hearn <mike@plan99.net> wrote:
+> Maybe you dislike that idea. It's so .... centralised. So let's say Gavin
+> commits his patch, because his authority is equal to all other committers.
+> Someone else rolls it back. Gavin sets up a cron job to keep committing the
+> patch. Game over.
+>
+> You cannot have committers fighting over what goes in and what doesn't.
+> That's madness. There must be a single decision maker for any given
+> codebase.
+
+Hmm, git repositories don't quite work like that. Instead, you should
+imagine everyone having a local copy of the git repository. Each
+developer synchronizes their git repository with other developers.
+They merge changes from specific remote branches that they have
+received. Each developer has their own branch and each developer is
+the "single decision maker" for the artifact that they compile.
+
+- Bryan
+http://heybryan.org/
+1 512 203 0507
+
+