From: Thomas Zander <thomas@thomaszander.se>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Cartographer
Date: Mon, 29 Dec 2014 12:49:45 +0100 [thread overview]
Message-ID: <26300405.yWTjxdDyQj@coldstorage> (raw)
In-Reply-To: <CANEZrP0GsuiCF4oHGnTnVXwUsc0dNBOTtusr_CFn+29SxYYwHw@mail.gmail.com>
On Monday 29. December 2014 11.30.42 Mike Hearn wrote:
> With the current DNS protocol you get an all or nothing choice
Its a seed. Not the protocol itself.
> Firstly, Peter, get help. I'm serious.
I think most would agree with me that, Mike, this answer is not just a little
over the line, its unacceptable behavior in any collaborative group.
Please be respectful and avoid ad-hominem attacks.
--
Thomas Zander
next prev parent reply other threads:[~2014-12-29 11:50 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 [this message]
2014-12-29 11:59 ` Peter Todd
2014-12-29 12:13 ` Btc Drak
2014-12-29 13:08 ` Mistr Bigs
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=26300405.yWTjxdDyQj@coldstorage \
--to=thomas@thomaszander.se \
--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