public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Bryan Bishop <kanzure@gmail.com>
To: Dr Adam Back <adam@cypherspace.org>, Bryan Bishop <kanzure@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] improving development model (Re: Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers
Date: Fri, 19 Jun 2015 06:35:28 -0500	[thread overview]
Message-ID: <CABaSBax92vJkz6Zu_4qBo00bt1TRXWJ3Z+8ic7FCDn2HLLd=0g@mail.gmail.com> (raw)
In-Reply-To: <CALqxMTFx6DF0Re+pCwB1AjYo6eYuKtX1cqUpo=wXmHSOsN74dQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 462 bytes --]

On Fri, Jun 19, 2015 at 5:45 AM, Dr Adam Back <adam@cypherspace.org> wrote:

> payment protocol layer in my view.  (If thats not obvious to some
> lurkers I elaborate on that argument  amongst other things here:
> https://www.youtube.com/watch?v=3dAdI3Gzodo )
>

Someone might find it more convenient to consume that in the form of text
instead:
http://diyhpl.us/wiki/transcripts/bitcoin-adam3us-fungibility-privacy/

- Bryan
http://heybryan.org/
1 512 203 0507

[-- Attachment #2: Type: text/html, Size: 1192 bytes --]

  reply	other threads:[~2015-06-19 11:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19  9:22 [Bitcoin-development] improving development model (Re: Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers Dr Adam Back
2015-06-19 10:45 ` Dr Adam Back
2015-06-19 11:35   ` Bryan Bishop [this message]
2015-06-19 12:02   ` Eric Lombrozo
2015-06-19 12:48     ` Marcel Jamin
2015-06-19 12:49       ` Eric Lombrozo
2015-06-19 12:02   ` Eric Lombrozo
2015-06-19 13:43   ` Mike Hearn
2015-06-20  2:59     ` Tom Harding
2015-06-19 16:05   ` Milly Bitcoin

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='CABaSBax92vJkz6Zu_4qBo00bt1TRXWJ3Z+8ic7FCDn2HLLd=0g@mail.gmail.com' \
    --to=kanzure@gmail.com \
    --cc=adam@cypherspace.org \
    --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