Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 742BDE8D for ; Wed, 30 Dec 2015 16:43:09 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-lf0-f51.google.com (mail-lf0-f51.google.com [209.85.215.51]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C576B169 for ; Wed, 30 Dec 2015 16:43:08 +0000 (UTC) Received: by mail-lf0-f51.google.com with SMTP id y184so228635410lfc.1 for ; Wed, 30 Dec 2015 08:43:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=vAMrikVXpjHLtLDjqai7T0wNiTcfEmeoSxkwxD25j4I=; b=0y1yILGNsdHtY5N5c8FKJDG+PgyPuny7EvNZnBDsaFAgH5Jk3wkdO/MWZ0Fzvd7FIk O6Nv4nNDpmoRHEhXjppfNeuYjQEuKmA2Kd597X3P7rMRfb5P+QSINg3veFjo6s7To9GB LeFc6g6Y9TJ599mI5N0oigjAQWDOZHJCIKuTH9Hv7GW4khmvCa9PJwudnnjZc7fiHpVc iEUWbkAcs8G5rNzucxyqLWy18V7apDdpuTha/EIAIrMYLMcH4cTT/xbTzTlByy9rH/gx eBP5SVD0mCquNYLWpPIMSiKkxm24miT+vOakTrvLUxkfwYXkuPZCa/8EjsF4qxbWG6aT lbhg== X-Received: by 10.25.83.193 with SMTP id h184mr3408991lfb.6.1451493786758; Wed, 30 Dec 2015 08:43:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.186.228 with HTTP; Wed, 30 Dec 2015 08:42:47 -0800 (PST) From: Marco Pontello Date: Wed, 30 Dec 2015 17:42:47 +0100 Message-ID: To: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a1142507e8db1da0528203bac X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Thu, 31 Dec 2015 23:05:34 +0000 Subject: [bitcoin-dev] BIP numbers X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2015 16:43:09 -0000 --001a1142507e8db1da0528203bac Content-Type: text/plain; charset=UTF-8 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! --001a1142507e8db1da0528203bac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Sorry to ask again but... what's up with the BIP = number assignments?

I thought that it was just more or less a for= mality, to avoid conflicts and BIP spamming. And that would be perfectly fi= ne.

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 officia= lity of sorts? But that would make little sense, since that should come eve= ntually with subsequents steps (like adding a BIP to the main repo, and eve= ntual 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.=C2=A0

<= br>

What I'm missing? Probably some historic context?=C2=A0

Thanks!

--001a1142507e8db1da0528203bac--