From: Marco Pontello <marcopon@gmail•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP numbers
Date: Wed, 30 Dec 2015 17:42:47 +0100 [thread overview]
Message-ID: <CAE0pACJf=aQFFTwRyWn+8SxS2P-v5FmG77kbC35rq_0p42CDEw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
Sorry to ask again but... what's up with the BIP number assignments?
I thought that it was just more or less a formality, to avoid conflicts and
BIP spamming. And that would be perfectly fine.
But since I see that it's a process that can take months (just looking at
the PR request list), it seems that something different is going on. Maybe
it's considered something that give an aura of officiality of sorts? But
that would make little sense, since that should come eventually with
subsequents steps (like adding a BIP to the main repo, and eventual
approvation).
Having # 333 assigned to a BIP, should just mean that's easy to refer to a
particular BIP.
That seems something that could be done quick and easily.
What I'm missing? Probably some historic context?
Thanks!
[-- Attachment #2: Type: text/html, Size: 926 bytes --]
next reply other threads:[~2015-12-30 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 16:42 Marco Pontello [this message]
2015-12-31 23:14 ` Peter Todd
2015-12-31 23:30 ` Adrian Macneil
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='CAE0pACJf=aQFFTwRyWn+8SxS2P-v5FmG77kbC35rq_0p42CDEw@mail.gmail.com' \
--to=marcopon@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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