From: Milly Bitcoin <milly@bitcoins•info>
To: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin mining idea
Date: Tue, 29 Sep 2015 20:07:31 -0400 [thread overview]
Message-ID: <560B27C3.3060404@bitcoins.info> (raw)
In-Reply-To: <CADm_WcaKCt0nSLAuohnCP9E4nvO2oj-ZQ6t1S_xHT7AQ5WqT6g@mail.gmail.com>
> Since 2011 and bitcoin-development, the list was always intended to
> focus on the highly technical bits of the core software, and avoid
> wandering into never-ending philosophical discussions. Example:
> http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2011-June/thread.html
What happened years ago is not really relevant as Bitcoin has changed
and the stakeholders have expanded. What is relevant is the actual
description. Whatever you want to discuss it should be clearly
described when people sign up.
Russ
next prev parent reply other threads:[~2015-09-30 0:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 17:53 Neil Haran
2015-09-28 13:33 ` Lauri Love
2015-09-29 5:47 ` Neil Haran
2015-09-29 5:56 ` Trevin Hofmann
2015-09-29 6:13 ` Milly Bitcoin
2015-09-29 21:07 ` Jeff Garzik
2015-09-29 22:58 ` Milly Bitcoin
2015-09-29 23:02 ` Jonathan Toomim (Toomim Bros)
2015-09-29 23:16 ` Milly Bitcoin
2015-09-29 23:54 ` Jeff Garzik
2015-09-30 0:07 ` Milly Bitcoin [this message]
2015-09-30 0:10 ` Jeff Garzik
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=560B27C3.3060404@bitcoins.info \
--to=milly@bitcoins$(echo .)info \
--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