public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: grarpamp <grarpamp@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] bitcoin pull requests
Date: Wed, 3 Apr 2013 11:52:49 -0400	[thread overview]
Message-ID: <CAD2Ti2-quRpfARLHw3riFpFihwYy2+R+4AW7Ovxq-W3qkzKptw@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpcZtsZ=p30hJtqLTBJPEE3eD=gQ+x6bKy46z0hc8XNB1Q@mail.gmail.com>

>> gpg signing commits, like the Linux kernel

> 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,
>
> * just before I click "pull", sneak rebases the branch to something evil


You might want to look at http://www.monotone.ca/, it does a good job
of integrating crypto and review primitives into the workflow.
It also has some reliable network distribution models (netsync) that work
well over things like Tor, in case a new developer (or old Satoshi) doesn't
wish to be in the public light.

http://www.monotone.ca/monotone.html

Once you have the crypto, it always boils down to human risk factors,
rogue, password, cracks, etc which are harder.



  reply	other threads:[~2013-04-03 15:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01  8:26 [Bitcoin-development] bitcoin pull requests Melvin Carvalho
2013-04-01 18:28 ` Petr Praus
2013-04-01 21:52   ` Melvin Carvalho
2013-04-01 22:10     ` Will
2013-04-01 22:27       ` Melvin Carvalho
2013-04-01 22:51         ` Roy Badami
2013-04-01 22:54           ` Roy Badami
2013-04-03  3:41             ` Wladimir
2013-04-03  3:51               ` Jeff Garzik
2013-04-03 15:52                 ` grarpamp [this message]
2013-04-03 16:05                   ` Gavin Andresen
2013-04-03 16:23                     ` grarpamp
     [not found]                       ` <CAAS2fgT06RHBO_0stKQAYLPB39ZAzaCVduFZJROjSzXUP4Db+g@mail.gmail.com>
2013-04-03 18:12                         ` grarpamp
2013-04-04  9:11                           ` Mike Hearn
2013-04-04 10:04                             ` Mike Hearn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAD2Ti2-quRpfARLHw3riFpFihwYy2+R+4AW7Ovxq-W3qkzKptw@mail.gmail.com \
    --to=grarpamp@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox