From: Tom Zander <tomz@freedommail•ch>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Classic 1.2.0 released
Date: Sat, 07 Jan 2017 16:15:30 +0100 [thread overview]
Message-ID: <1758904.yvpRk0eHcr@cherry> (raw)
In-Reply-To: <CABr1YTfc0BZ21-mwMohqo8_v8D1QnYiGB_SMeCLwFChY2MV_zA@mail.gmail.com>
On Saturday, 7 January 2017 00:55:19 CET Eric Lombrozo wrote:
> Your release announcement does not make it clear that Bitcoin Classic is
> incompatible with the current Bitcoin network and its consensus rules.
To explain why I didn't write that;
Bitcoin Classic is not incompatible with the current Bitcoin network and its
consensus rules.
--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel
next prev parent reply other threads:[~2017-01-07 15:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 10:16 Tom Zander
2017-01-07 8:13 ` Jonas Schnelli
2017-01-07 8:55 ` Eric Lombrozo
2017-01-07 15:15 ` Tom Zander [this message]
2017-01-07 20:12 ` Chris Priest
2017-01-07 20:17 ` David Vorick
2017-01-07 20:26 ` Chris Priest
2017-01-07 21:14 ` Eric Voskuil
2017-01-07 23:10 ` Aymeric Vitte
2017-01-07 23:49 ` Eric Voskuil
2017-01-08 0:28 ` Eric Lombrozo
2017-01-08 1:58 ` Chris Priest
2017-01-07 21:15 ` Btc Drak
2017-01-07 23:08 ` Tom Zander
2017-01-08 0:32 ` Eric Voskuil
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=1758904.yvpRk0eHcr@cherry \
--to=tomz@freedommail$(echo .)ch \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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