From: Wladimir <laanwj@gmail•com>
To: Luke Dashjr <luke@dashjr•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed BIP status changes
Date: Thu, 16 Oct 2014 08:22:04 +0200 [thread overview]
Message-ID: <CA+s+GJAhJTXZwotBzGMh_D3ZadjuP-UtOV+Xv+pBMZ7QOH21GQ@mail.gmail.com> (raw)
In-Reply-To: <201410160436.52259.luke@dashjr.org>
>
> Shouldn't we be doing this in a GitHub PR rather than spamming up the ML?
Not really. BIP changes should be discussed on the mailing list,
that's the way to get community consensus (as specified in BIP1).
Wladimir
next prev parent reply other threads:[~2014-10-16 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 8:47 Wladimir
2014-10-16 4:29 ` Matt Corallo
2014-10-16 4:36 ` Luke Dashjr
2014-10-16 6:22 ` Wladimir [this message]
2014-10-16 6:46 ` Luke Dashjr
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=CA+s+GJAhJTXZwotBzGMh_D3ZadjuP-UtOV+Xv+pBMZ7QOH21GQ@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)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