Return-Path: <aj@erisian.com.au>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id B7777C0037
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 19 Jan 2024 00:46:21 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 7EE4440426
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 19 Jan 2024 00:46:21 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 7EE4440426
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
 by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id cpnxW-ynDCXI
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 19 Jan 2024 00:46:20 +0000 (UTC)
Received: from cerulean.erisian.com.au (azure.erisian.com.au [172.104.61.193])
 by smtp2.osuosl.org (Postfix) with ESMTPS id 2114440025
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 19 Jan 2024 00:46:20 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 2114440025
Received: from aj@azure.erisian.com.au
 by cerulean.erisian.com.au with esmtpsa (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2)
 (envelope-from <aj@erisian.com.au>)
 id 1rQd1R-0006sS-LG; Fri, 19 Jan 2024 10:46:16 +1000
Received: by email (sSMTP sendmail emulation); Fri, 19 Jan 2024 10:46:10 +1000
Date: Fri, 19 Jan 2024 10:46:10 +1000
From: Anthony Towns <aj@erisian.com.au>
To: "David A. Harding" <dave@dtrt.org>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <ZanGUhKRJY2pgZuf@erisian.com.au>
References: <Zac+rMC/c+qTmSxY@erisian.com.au>
 <6f3ce219d7df09c80e8063579555de06@dtrt.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6f3ce219d7df09c80e8063579555de06@dtrt.org>
X-Spam_score: -0.0
X-Spam_bar: /
Subject: Re: [bitcoin-dev] BIP process friction
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jan 2024 00:46:21 -0000

On Thu, Jan 18, 2024 at 05:41:14AM -1000, David A. Harding via bitcoin-dev wrote:
> Question: is there a recommended way to produce a shorter identifier for
> inline use in reading material?  For example, for proposal
> BIN-2024-0001-000, I'm thinking:
> 
> - BIN24-1 (references whatever the current version of the proposal is)
> - BIN24-1.0 (references revision 0)
> 
> I think that doesn't look too bad even if there are over 100 proposals a
> year, with some of them getting into over a hundred revisions:
> 
> - BIN24-123
> - BIN24-123.123

Having lived through y2k, two-digit years give me the ick, but otherwise
sure.

Cheers,
aj, that's how the kids who didn't live through y2k say it, right?