From: Pindar Wong <pindar.wong@gmail•com>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP for standard multi-signature P2SH addresses
Date: Thu, 12 Mar 2015 07:50:08 +0800 [thread overview]
Message-ID: <CAM7BtUrMzCa_MhMgqW_JVGy4Dia3DYvC_yetjW+zqH8wOuZyMQ@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgTvqTmkujVKLryH+iX7JFd=jJp89p7bggrdmRHAbWiNxQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
Understood... perhaps just add something like:
'After copy-editing and acceptance,* a BIP number is assigned* and it will
be published here.'?
https://en.bitcoin.it/wiki/Bitcoin_Improvement_Proposals
p.
On Thu, Mar 12, 2015 at 7:34 AM, Gregory Maxwell <gmaxwell@gmail•com> wrote:
> On Wed, Mar 11, 2015 at 11:24 PM, Pindar Wong <pindar.wong@gmail•com>
> wrote:
> > Perhaps at some point consider introducing something akin to a
> > 'Bitcoin-Draft' (BD) status with some autoexpiry period?
> >
> > I understand that the Internet Engineering Task Force (IETF) has the
> > concept of 'Internet Drafts" (ID) and this looks like it has worked for
> them
> > so far.
>
> Thats more or less what posting to the list is supposed to be.
> Creating a draft document requires no approval, beyond filling out the
> right form.
>
> Perhaps calling out that as a distinct step would be better, indeed.
>
[-- Attachment #2: Type: text/html, Size: 1470 bytes --]
next prev parent reply other threads:[~2015-03-11 23:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 11:45 Thomas Kerin
2015-03-11 17:16 ` Mike Hearn
2015-03-11 20:16 ` Gregory Maxwell
2015-03-11 23:24 ` Pindar Wong
2015-03-11 23:34 ` Gregory Maxwell
2015-03-11 23:50 ` Pindar Wong [this message]
2015-03-11 23:11 ` devrandom
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=CAM7BtUrMzCa_MhMgqW_JVGy4Dia3DYvC_yetjW+zqH8wOuZyMQ@mail.gmail.com \
--to=pindar.wong@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@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