From: Gavin Andresen <gavinandresen@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP21 bitcoin URIs and HTML5
Date: Wed, 24 Apr 2013 10:51:57 -0400 [thread overview]
Message-ID: <CABsx9T0Apu=ice=QdQpOb3LVTv9HcTjTmbb5KzZ3+o8CuF3kzg@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP2OPU8cpvUJ0B8z00PPp6jOGCjQ1ipZ9mq8_LSLo4Rebg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
> 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.
I vote for a new meta-data item in the BIP header:
Corrected: <date>
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 570 bytes --]
next prev parent reply other threads:[~2013-04-24 14:52 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 [this message]
2013-04-24 16:37 ` Gregory Maxwell
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='CABsx9T0Apu=ice=QdQpOb3LVTv9HcTjTmbb5KzZ3+o8CuF3kzg@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/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