From: Vitalik Buterin <v@buterin•com>
To: Alan Reiner <etotheipi@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin-development Digest, Vol 40, Issue 9
Date: Tue, 23 Sep 2014 15:57:10 -0400 [thread overview]
Message-ID: <CAH8WSafgyoq17caFhPpZxAErfms1GvKGG+G9Kz2LmvahphJ69g@mail.gmail.com> (raw)
In-Reply-To: <CALf2ePwooCNsK72GLXXSC7v-ucyqpJfB=K8euSusFBHmJ7UG8w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 30 bytes --]
Okay I see, that makes sense.
[-- Attachment #2: Type: text/html, Size: 82 bytes --]
prev parent reply other threads:[~2014-09-23 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.358444.1411492141.2178.bitcoin-development@lists.sourceforge.net>
2014-09-23 17:57 ` Vitalik Buterin
2014-09-23 18:45 ` Alan Reiner
2014-09-23 19:57 ` Vitalik Buterin [this message]
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=CAH8WSafgyoq17caFhPpZxAErfms1GvKGG+G9Kz2LmvahphJ69g@mail.gmail.com \
--to=v@buterin$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=etotheipi@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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