From: Mats Henricson <mats@henricson.se>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Meta suggestions for this block size debate
Date: Tue, 02 Jun 2015 00:22:01 +0200 [thread overview]
Message-ID: <556CDB09.8050906@henricson.se> (raw)
Hi!
My fingers have been itching many times now, this debate
drives me nuts.
I just wish all posters could follow two simple principles:
1. Read up. Yes. All of what has been written. Yes, it will
take many hours. But if you're rehashing what other
smarter people have said over and over before, you're
wasting hundreds of peoples time. Please don't.
2. Be helpful. Suggest alternatives. Just cristizising is
just destructive. If you want no change, then say so.
Mats
next reply other threads:[~2015-06-01 22:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 22:22 Mats Henricson [this message]
2015-06-02 3:02 ` [Bitcoin-development] Meta suggestions for this block size debate gabe appleton
2015-06-02 3:32 ` Ethan Heilman
2015-06-02 3:52 ` gabe appleton
2015-06-06 3:34 ` Pindar Wong
2015-06-06 6:28 ` gabe appleton
2015-06-06 6:34 ` Pindar Wong
2015-06-06 6:37 ` gabe appleton
2015-06-06 6:39 ` Pindar Wong
2015-06-06 6:41 ` gabe appleton
2015-06-08 0:55 ` gabe appleton
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=556CDB09.8050906@henricson.se \
--to=mats@henricson.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