From: "cipher anthem" <cipher.anthem@gmx.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Fwd: Block Size Increase Requirements
Date: Tue, 2 Jun 2015 13:19:48 +0200 [thread overview]
Message-ID: <trinity-cecc9151-6544-43e0-a958-ac9e4d7699ff-1433243988016@3capp-mailcom-bs06> (raw)
[-- Attachment #1: Type: text/html, Size: 6830 bytes --]
next reply other threads:[~2015-06-02 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 11:19 cipher anthem [this message]
2015-06-02 11:26 ` [Bitcoin-development] Fwd: Block Size Increase Requirements Mike Hearn
2015-06-02 11:43 ` Nathan Cook
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=trinity-cecc9151-6544-43e0-a958-ac9e4d7699ff-1433243988016@3capp-mailcom-bs06 \
--to=cipher.anthem@gmx.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