From: Luke Dashjr <luke@dashjr•org>
To: Wladimir <laanwj@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Proposed BIP status changes
Date: Thu, 16 Oct 2014 04:36:51 +0000 [thread overview]
Message-ID: <201410160436.52259.luke@dashjr.org> (raw)
In-Reply-To: <CA+s+GJApfj5OAxGyHG9CsmRHTpAQBgC44iU2U99LwNGNZDATBw@mail.gmail.com>
On Wednesday, October 15, 2014 8:47:18 AM Wladimir wrote:
> These BIPs should go to Final state - they are implemented all over
> the place, and are thus entirely fixed in place now. Any changes would
> require a new BIP as amandment:
>
> - BIP 14 (BIP Protocol Version and User Agent)
ACK
> - BIP 21 (URI Scheme)
ACK
> - BIP 22 (getblocktemplate - Fundamentals)
ACK
> - BIP 31 (Pong Message)
ACK
> - BIP 34 (Block v2, Height in coinbase)
ACK
> - BIP 35 (mempool message)
ACK
> - BIP 37 (Bloom filtering)
>
> Let me know if you (don't) agree.
Shouldn't we be doing this in a GitHub PR rather than spamming up the ML?
Luke
next prev parent reply other threads:[~2014-10-16 4:37 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 [this message]
2014-10-16 6:22 ` Wladimir
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=201410160436.52259.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@gmail$(echo .)com \
/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