From: Chris Priest <cp368202@ohiou•edu>
To: Eric Lombrozo <elombrozo@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Classic 1.2.0 released
Date: Sat, 7 Jan 2017 17:58:27 -0800 [thread overview]
Message-ID: <CAAcC9ysOn0CkEO53NnQPnvVJ-PzCmrHYRqYcdZBqBfDbYnv5Vw@mail.gmail.com> (raw)
In-Reply-To: <CABr1YTfRDUQNivebMvsONV0na7j_sEyw3gii+5r4v8txu+O68w@mail.gmail.com>
Its too bad you're not the one who decides what gets posted here or
not. If you don't like whats being discussed, then don't open those
emails.
On 1/7/17, Eric Lombrozo via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> Can you guys please take this discussion elsewhere? Perhaps to
> bitcoin-discuss? This is not the place to rehash discussions that have
> taken place a million times already. The behavior of the network under
> contentious hard forks has been discussed ad nauseum. This mailing list is
> for the discussion of new ideas and proposals.
>
> Much appreciated. Thanks.
>
> On Sat, Jan 7, 2017 at 3:49 PM, Eric Voskuil via bitcoin-dev <
> bitcoin-dev@lists•linuxfoundation.org> wrote:
>
>> On 01/07/2017 03:10 PM, Aymeric Vitte via bitcoin-dev wrote:
>> > Still wondering why you guys don't care about the ridiculous number of
>> > full nodes, no incentive to run one and what would happen if someone
>> > were to control a majority of full nodes
>>
>> The level of control over a majority of full nodes is irrelevant. If
>> this was truly a measure of control over Bitcoin someone would simply
>> spin up a bunch of nodes and take control at trivial cost.
>>
>> e
>>
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists•linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>
>
next prev parent reply other threads:[~2017-01-08 1:58 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
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 [this message]
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=CAAcC9ysOn0CkEO53NnQPnvVJ-PzCmrHYRqYcdZBqBfDbYnv5Vw@mail.gmail.com \
--to=cp368202@ohiou$(echo .)edu \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=elombrozo@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