From: Harald Schilly <harald@schil.ly>
To: Michael Gronager <gronager@ceptacle.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] off-topic: bitcoin-forum...
Date: Sun, 19 Feb 2012 17:42:36 +0100 [thread overview]
Message-ID: <CAGG4CB7HY4z0uvRXxc2S-Bmg9JdVFPDhJhLdWff2BE8eje3JTg@mail.gmail.com> (raw)
In-Reply-To: <15A9E3BE-3288-4CDC-8243-05669298CDB0@ceptacle.com>
On Sun, Feb 19, 2012 at 17:38, Michael Gronager <gronager@ceptacle.com> wrote:
> In the expectation of a embarrassingly simple answer...
you probably need to be whitelisted, but i'm not sure.
https://bitcointalk.org/index.php?topic=15911.0
h
next prev parent reply other threads:[~2012-02-19 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-19 16:38 [Bitcoin-development] off-topic: bitcoin-forum Michael Gronager
2012-02-19 16:42 ` Harald Schilly [this message]
2012-02-19 16:45 ` Michael Grønager
2012-02-19 16:46 ` Harald Schilly
2012-02-19 16:51 ` Wladimir
2012-02-19 21:32 ` grarpamp
2012-02-19 22:57 ` Daniel F
2012-02-20 0:13 ` grarpamp
2012-02-20 2:32 ` Daniel F
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=CAGG4CB7HY4z0uvRXxc2S-Bmg9JdVFPDhJhLdWff2BE8eje3JTg@mail.gmail.com \
--to=harald@schil.ly \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gronager@ceptacle.com \
/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