From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] All pre-BIP BIPs are not valid
Date: Sun, 29 Jan 2012 18:10:30 -0500 [thread overview]
Message-ID: <201201291810.31581.luke@dashjr.org> (raw)
In-Reply-To: <1327878150.23803.4.camel@BMThinkPad.lan.bluematt.me>
On Sunday, January 29, 2012 6:02:30 PM Matt Corallo wrote:
> I have to say, I agree with Luke here, this was Finalized a long time
> ago. The version that was agreed on can be seen at
> https://en.bitcoin.it/wiki/BIP_0021
No, that never had a consensus.
> Also see https://bitcointalk.org/index.php?topic=6205.0 and Luke's three
> biased polls at
> https://bitcointalk.org/index.php?topic=6206.0
> https://bitcointalk.org/index.php?topic=6207.0
> https://bitcointalk.org/index.php?topic=6208.0
As everyone can observe from your bitcointalk links, you didn't begin trolling
until months after the URI Scheme was Finalized (in January 2011).
prev parent reply other threads:[~2012-01-29 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 22:40 [Bitcoin-development] All pre-BIP BIPs are not valid Amir Taaki
2012-01-29 22:50 ` Luke-Jr
2012-01-29 23:02 ` Matt Corallo
2012-01-29 23:10 ` Luke-Jr [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=201201291810.31581.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/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