public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Anthony Towns <aj@erisian•com.au>
To: "David A. Harding" <dave@dtrt•org>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP process friction
Date: Fri, 19 Jan 2024 10:46:10 +1000	[thread overview]
Message-ID: <ZanGUhKRJY2pgZuf@erisian.com.au> (raw)
In-Reply-To: <6f3ce219d7df09c80e8063579555de06@dtrt.org>

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?


  reply	other threads:[~2024-01-19  0:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17  2:42 Anthony Towns
2024-01-17  6:55 ` Christopher Allen
2024-01-17 16:45   ` Luke Dashjr
2024-01-17 17:29     ` Michael Folkson
2024-01-18 18:00       ` Peter Todd
2024-01-19 19:27         ` Michael Folkson
2024-01-18 15:41 ` David A. Harding
2024-01-19  0:46   ` Anthony Towns [this message]
2024-01-19  2:33     ` Karl-Johan Alm
2024-01-18 16:47 ` alicexbt
2024-01-18 17:42   ` Peter Todd

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=ZanGUhKRJY2pgZuf@erisian.com.au \
    --to=aj@erisian$(echo .)com.au \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=dave@dtrt$(echo .)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