public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Milly Bitcoin <milly@bitcoins•info>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin mining idea
Date: Tue, 29 Sep 2015 18:58:37 -0400	[thread overview]
Message-ID: <560B179D.6090007@bitcoins.info> (raw)
In-Reply-To: <CADm_WcYqb82VRNrSFMgJgqz38YA9Ew28ZWz4kq_8aM4uhWcbHQ@mail.gmail.com>

On 9/29/2015 5:07 PM, Jeff Garzik via bitcoin-dev wrote:
> This is off-topic for this list.

You like to go around pretending you are in charge and telling people 
what to do.  You have no such authority and your time is probably better 
spent reviewing your company's Bitcoin handling and security procedures 
instead of trying to bully people all the time.

Russ




  reply	other threads:[~2015-09-29 22:58 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 [this message]
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
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=560B179D.6090007@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