From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: References: <554A91BE.6060105@bluematt.me> Date: Thu, 7 May 2015 09:18:17 -0500 Message-ID: From: Bryan Bishop To: Mike Hearn , Bryan Bishop 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 Subject: Re: [Bitcoin-development] Block Size Increase 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, 07 May 2015 14:18:26 -0000 On Thu, May 7, 2015 at 9:05 AM, Mike Hearn 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