Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UNEqa-00042f-1b for bitcoin-development@lists.sourceforge.net; Wed, 03 Apr 2013 03:58:52 +0000 X-ACL-Warn: Received: from mail-pa0-f53.google.com ([209.85.220.53]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UNEqY-0000SN-Kv for bitcoin-development@lists.sourceforge.net; Wed, 03 Apr 2013 03:58:52 +0000 Received: by mail-pa0-f53.google.com with SMTP id bh4so663634pad.12 for ; Tue, 02 Apr 2013 20:58:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=EYl2Dk8+5cZKtdErjBrFPFnj5gKK3/EUvmZItzDiPAA=; b=YhVvqGynp4yQjdPaiGT5cTheXviNG6xKTj59zUe98xgT9LrcZjNWfvtelgewBwUpzb FJy8KTjtWznmLL7JQQR7kBjcLEmcKX/6BhLeDdGb7+0gLirmaUXCWvl9Kb7P0Mt1mlX5 AGEILIbzkXQpQGM9wEghsOaOaxWhFZXxYS453eMUg4QV6JiqCC+ovgwDBqPs3FHgwgcm w1cQtM6Rd7og0bxqPzNZBgaV4wVYmUQZXX7phsSVDXwj3Csa7EBWye685MhC2TizKvN8 jA3bsMSfCt2Mb660Hs/j2HxUVoPKoD/+BHCBoVu+IRW9yMHrBYRfoCs90T+dy/mwIsOH eUdQ== MIME-Version: 1.0 X-Received: by 10.66.161.33 with SMTP id xp1mr843582pab.36.1364961105522; Tue, 02 Apr 2013 20:51:45 -0700 (PDT) Received: by 10.68.253.35 with HTTP; Tue, 2 Apr 2013 20:51:45 -0700 (PDT) X-Originating-IP: [99.43.178.25] In-Reply-To: References: <20130401225107.GU65880@giles.gnomon.org.uk> <20130401225417.GV65880@giles.gnomon.org.uk> Date: Tue, 2 Apr 2013 23:51:45 -0400 Message-ID: From: Jeff Garzik To: Wladimir Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmX8dGMpQO5rxI6tgsd3GmETxzt3OAn9Gr6l/OmKsL8SJeSBT+2AvOcM4d6OMoq8ZXTXbuw X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1UNEqY-0000SN-Kv Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] bitcoin pull requests 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: Wed, 03 Apr 2013 03:58:52 -0000 On Tue, Apr 2, 2013 at 11:41 PM, Wladimir wrote: > Maybe now that bitcoin is growing out of the toy phase it's an idea to start > gpg signing commits, like the Linux kernel > (https://lwn.net/Articles/466468/). > > But I suppose then we can't use github anymore to merge as-is and need > manual steps? Correct, that rules out github, AFAICS. Though, honestly, when I ACK that means I read the code, which is more important than the author really. github seems fine for that still, though I do wonder if there is a race possible, * sneak uploads innocent branch sneak/bitcoin.git #innocent * sneak creates pull req * just before I click "pull", sneak rebases the branch to something evil -- Jeff Garzik exMULTI, Inc. jgarzik@exmulti.com