From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XL9eL-0008Ua-PM for bitcoin-development@lists.sourceforge.net; Sat, 23 Aug 2014 11:38:25 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.177 as permitted sender) client-ip=209.85.213.177; envelope-from=pieter.wuille@gmail.com; helo=mail-ig0-f177.google.com; Received: from mail-ig0-f177.google.com ([209.85.213.177]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XL9eD-0003aM-Eq for bitcoin-development@lists.sourceforge.net; Sat, 23 Aug 2014 11:38:25 +0000 Received: by mail-ig0-f177.google.com with SMTP id hn18so855257igb.4 for ; Sat, 23 Aug 2014 04:38:10 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.142.100 with SMTP id rv4mr4060997igb.43.1408793890058; Sat, 23 Aug 2014 04:38:10 -0700 (PDT) Received: by 10.50.156.135 with HTTP; Sat, 23 Aug 2014 04:38:09 -0700 (PDT) In-Reply-To: <20140823061701.GQ22640@nl.grid.coop> References: <2302927.fMx0I5lQth@1337h4x0r> <20140823061701.GQ22640@nl.grid.coop> Date: Sat, 23 Aug 2014 13:38:09 +0200 Message-ID: From: Pieter Wuille To: Troy Benjegerdes Content-Type: text/plain; charset=ISO-8859-1 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 (pieter.wuille[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: 1XL9eD-0003aM-Eq Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Reconsidering github 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: Sat, 23 Aug 2014 11:38:25 -0000 On Sat, Aug 23, 2014 at 8:17 AM, Troy Benjegerdes wrote: > On Fri, Aug 22, 2014 at 09:20:11PM +0200, xor wrote: >> On Tuesday, August 19, 2014 08:02:37 AM Jeff Garzik wrote: >> > It would be nice if the issues and git repo for Bitcoin Core were not >> > on such a centralized service as github, nice and convenient as it is. >> >> Assuming there is a problem with that usually is caused by using Git the wrong >> way or not knowing its capabilities. Nobody can modify / insert a commit >> before a GnuPG signed commit / tag without breaking the signature. >> More detail at the bottom at [1], I am sparing you this here because I suspect >> you already know it and there is something more important I want to stress: Note that we're generally aiming (though not yet enforcing) to have merges done through the github-merge tool, which performs the merge locally, shows the resulting diff, compares it with the merge done by github, and GnuPG signs it. That allows using github as easy-access mechanism for people to contribute and inspect, while having a higher security standard for the actual changes done to master. -- Pieter