From: Gregory Maxwell <gmaxwell@gmail•com>
To: Alan Reiner <etotheipi@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Some PR preparation
Date: Tue, 12 Mar 2013 11:39:48 -0700 [thread overview]
Message-ID: <CAAS2fgQVLb1L=LZvYz_rf7Auim_oKRmVp+6NC+5AFjyD9NQe5A@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgSZfsAbfWqst+DVjKpaJ5dh7u934rp4p=AE8pbni_VSiw@mail.gmail.com>
On Tue, Mar 12, 2013 at 11:09 AM, Gregory Maxwell <gmaxwell@gmail•com> wrote:
> On Tue, Mar 12, 2013 at 10:35 AM, Peter Vessenes <peter@coinlab•com> wrote:
>> Can some enterprising soul determine if there were any double-spend attempts?
>> I'm assuming no, and if that's the case, we should talk about that publicly.
[snip]
> I agree it would be good to confirm no one was ripped off, even though
> we can't say there weren't any attempts.
https://bitcointalk.org/index.php?topic=152348.msg1616747#msg1616747
next prev parent reply other threads:[~2013-03-12 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 7:03 Alan Reiner
2013-03-12 12:10 ` Luke-Jr
2013-03-12 16:55 ` Alan Reiner
2013-03-12 17:35 ` Peter Vessenes
2013-03-12 18:09 ` Gregory Maxwell
2013-03-12 18:39 ` Gregory Maxwell [this message]
2013-03-12 19:53 ` Christian Decker
2013-03-12 20:09 ` Peter Vessenes
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='CAAS2fgQVLb1L=LZvYz_rf7Auim_oKRmVp+6NC+5AFjyD9NQe5A@mail.gmail.com' \
--to=gmaxwell@gmail$(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