From: Martin Sustrik <sustrik@250bpm•com>
To: Jean-Paul Kogelman <jeanpaulkogelman@me•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] A critique of bitcoin open source community
Date: Mon, 21 Oct 2013 09:28:39 +0200 [thread overview]
Message-ID: <5264D7A7.2080308@250bpm.com> (raw)
In-Reply-To: <DEE378F5-8057-4C3C-8905-B1409E963521@me.com>
On 21/10/13 09:07, Jean-Paul Kogelman wrote:
> The list comes from BIP 1.
Sorry, I haven't meant you personally. It was just a generic question
about using existing process instead of inventing a new one on the go.
>> Have it been considered to do this via IETF? The process there is hardened by 40 years of experience and 7000+ RFCs. Probably better than anything you can devise yourself.
>>
>> Martin
>
next prev parent reply other threads:[~2013-10-21 7:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-19 16:38 Mitar
2013-10-19 16:50 ` Melvin Carvalho
2013-10-19 20:40 ` Gregory Maxwell
2013-10-19 21:09 ` Mitar
2013-10-19 21:16 ` Jean-Paul Kogelman
2013-10-19 22:29 ` Luke-Jr
2013-10-19 23:20 ` Gregory Maxwell
2013-10-19 23:35 ` Jean-Paul Kogelman
2013-10-19 23:57 ` Peter Todd
2013-10-20 0:52 ` Jean-Paul Kogelman
2013-10-20 22:43 ` Peter Todd
2013-10-20 23:11 ` Peter Todd
2013-10-21 0:27 ` Jeff Garzik
2013-10-21 6:25 ` Peter Todd
2013-10-21 6:40 ` Jean-Paul Kogelman
2013-10-21 6:43 ` Peter Todd
2013-10-21 6:52 ` Jean-Paul Kogelman
2013-10-21 7:03 ` Martin Sustrik
2013-10-21 7:07 ` Jean-Paul Kogelman
2013-10-21 7:28 ` Martin Sustrik [this message]
2013-10-21 9:36 ` Melvin Carvalho
2013-10-21 9:44 ` Arto Bendiken
2013-10-21 9:49 ` Jean-Paul Kogelman
2013-10-21 10:21 ` Jorge Timón
2013-10-20 10:00 ` Wladimir
2013-10-19 23:21 ` Jean-Paul Kogelman
2013-10-19 23:22 ` Jean-Paul Kogelman
2013-10-19 22:33 ` Mike Hearn
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=5264D7A7.2080308@250bpm.com \
--to=sustrik@250bpm$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jeanpaulkogelman@me$(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