From: bgroff@lavabit•com
To: "Alex Waters" <ampedal@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin Enhancement Proposals (BEPS)
Date: Mon, 19 Sep 2011 12:01:24 -0400 (EDT) [thread overview]
Message-ID: <21269.192.251.226.206.1316448084.squirrel@lavabit.com> (raw)
In-Reply-To: <CAL0fb61B6bqGMhWtCgvy0xwfHQ_nvmhbb9uLJQWx3biENhVJNw@mail.gmail.com>
> http://www.python.org/dev/peps/ is a good reference if you're
> interested in seeing how PEPs work in action. I would be more than
> willing to maintain a similar index if that's what people want.
Would the multi-signature proposal be a good test case for BEP-0002?
https://gist.github.com/dba89537d352d591eb36
I can reformat it and email here.
Gavin has a competing one: https://gist.github.com/39158239e36f6af69d6f
and I have a pull request matching a previous version of my proposal.
--
Bobby Groff
next prev parent reply other threads:[~2011-09-19 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 1:04 Luke-Jr
2011-09-19 3:22 ` Alex Waters
2011-09-19 16:01 ` bgroff [this message]
2011-09-19 16:57 ` Gavin Andresen
2011-09-19 17:23 ` Alex Waters
2011-09-20 2:06 ` Amir Taaki
2011-09-23 19:45 ` Daniel F
2011-09-25 3:27 ` Amir Taaki
-- strict thread matches above, loose matches on Subject: below --
2011-09-19 0:31 Amir Taaki
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=21269.192.251.226.206.1316448084.squirrel@lavabit.com \
--to=bgroff@lavabit$(echo .)com \
--cc=ampedal@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.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