From: Ryan Grant <bitcoin-dev@rgrant.org>
To: Jeremy <jlrubin@mit.edu>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Cc: Bitcoin Discuss <bitcoin-discuss@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] 1 Year bitcoin-dev Moderation Review
Date: Sun, 9 Oct 2016 22:31:54 +0200 [thread overview]
Message-ID: <CAMnpzfqiWuivxTLqoC-f=7XuRnU_Rhyves9CnLkA_LPLVwygmg@mail.gmail.com> (raw)
In-Reply-To: <CAD5xwhgayR9CgfcypCwGEDyubE4z-mXEjxDmGh09GYO8nhm3Ow@mail.gmail.com>
Maybe bitcoin-discuss should have been opt-out rather than opt-in.
Dear moderators, what is the subscription count to bitcoin-discuss,
and bitcoin-dev?
next prev parent reply other threads:[~2016-10-09 20:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 10:26 [bitcoin-dev] 1 Year bitcoin-dev Moderation Review Jeremy
2016-10-09 20:31 ` Ryan Grant [this message]
2016-10-10 7:38 ` Henning Kopp
2016-10-10 15:34 ` Dave Scotese
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='CAMnpzfqiWuivxTLqoC-f=7XuRnU_Rhyves9CnLkA_LPLVwygmg@mail.gmail.com' \
--to=bitcoin-dev@rgrant.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=bitcoin-discuss@lists.linuxfoundation.org \
--cc=jlrubin@mit.edu \
/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