From: "Pavel Janík" <Pavel@Janik.cz>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] On bitcoin-dev list admin and list noise
Date: Tue, 29 Sep 2015 19:59:18 +0200 [thread overview]
Message-ID: <772BA950-0EFE-4D10-9F6A-5916163A21AA@Janik.cz> (raw)
In-Reply-To: <CA+w+GKR3CYGZEJ9c9uwuuPvYgQEOH=gUVP_SN4Edfx7-m_p1cA@mail.gmail.com>
> On 29 Sep 2015, at 19:29, Mike Hearn via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> There's a simple way to cut down on "noise" that doesn't involve people shouting OFFTOPIC at each other: the maintainer needs to resolve discussions by making decisions and saying, this is how Core does it.
Looks like you are mixing the maintainer of the Bitcoin Core with the bitcoin-dev mailing list moderator. Intentionally?
--
Pavel Janík
prev parent reply other threads:[~2015-09-29 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 15:44 [bitcoin-dev] On bitcoin-dev list admin and list noise Jeff Garzik
2015-09-29 16:38 ` Santino Napolitano
2015-09-29 17:07 ` Mark Friedenbach
2015-09-29 17:29 ` Mike Hearn
2015-09-29 17:59 ` Pavel Janík [this message]
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=772BA950-0EFE-4D10-9F6A-5916163A21AA@Janik.cz \
--to=pavel@janik.cz \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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