From: Mistr Bigs <misterbg6@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Cartographer
Date: Mon, 29 Dec 2014 14:08:52 +0100 [thread overview]
Message-ID: <CABssiCpUTbNQZtsAJPJwU9mDxXR71ubBtDsA1J9fwgE8sxNo=g@mail.gmail.com> (raw)
In-Reply-To: <CADJgMzsL26G1YRK+gBfHx-=XOKVDQjj0=sdF-j3dur1Zux9Oew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 126 bytes --]
As an outside observer, I have to say I also found Peter's sardonic message
tone inappropriate for furthering the discussion.
[-- Attachment #2: Type: text/html, Size: 155 bytes --]
prev parent reply other threads:[~2014-12-29 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-28 18:25 [Bitcoin-development] Cartographer Mike Hearn
2014-12-29 8:47 ` Thomas Zander
2014-12-29 10:39 ` Peter Todd
2014-12-29 11:30 ` Mike Hearn
2014-12-29 11:49 ` Thomas Zander
2014-12-29 11:59 ` Peter Todd
2014-12-29 12:13 ` Btc Drak
2014-12-29 13:08 ` Mistr Bigs [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='CABssiCpUTbNQZtsAJPJwU9mDxXR71ubBtDsA1J9fwgE8sxNo=g@mail.gmail.com' \
--to=misterbg6@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