From: Gregory Maxwell <gmaxwell@gmail•com>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP21 bitcoin URIs and HTML5
Date: Wed, 24 Apr 2013 09:37:18 -0700 [thread overview]
Message-ID: <CAAS2fgRtq5J4HAeQGTfKc+vQZ9eo1Qw4nc=t2_Pu3KAuE_3WGQ@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T0Apu=ice=QdQpOb3LVTv9HcTjTmbb5KzZ3+o8CuF3kzg@mail.gmail.com>
On Wed, Apr 24, 2013 at 7:51 AM, Gavin Andresen <gavinandresen@gmail•com> wrote:
>> Ian pointed out some errors in the BIP21 spec. What's the process for
>> amending the BIP? Do we need to create a new one and mark the old one as
>> replaced, or can we just fix it in place given the relatively exotic nature
>> of most of the issues?
> Those all sound like bugs in the BIP; I think they should just be fixed, I
> don't think we need a new BIP.
Yup. Corrections are fine, esp ones which are not gratuitously incompatible.
next prev parent reply other threads:[~2013-04-24 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 7:42 Mike Hearn
2013-04-24 13:35 ` Andreas Schildbach
2013-04-24 14:51 ` Gavin Andresen
2013-04-24 16:37 ` Gregory Maxwell [this message]
2013-05-02 12:53 ` Mike Hearn
2013-04-24 16:21 ` Melvin Carvalho
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='CAAS2fgRtq5J4HAeQGTfKc+vQZ9eo1Qw4nc=t2_Pu3KAuE_3WGQ@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@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