From: Matt Whitlock <bip@mattwhitlock•name>
To: "David Barnes | Bitcoin Co. Ltd." <david.barnes@bitcoin•co.th>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP0074 Draft (Dynamic Rate Lookup)
Date: Fri, 17 Jul 2015 08:24:24 -0400 [thread overview]
Message-ID: <15824042.UJUZ1yd9UW@crushinator> (raw)
In-Reply-To: <55A8C1EF.8050603@bitcoin.co.th>
You should rename your file to something like "bip-draft-dynamic-rate-lookup". Using an arbitrary BIP number will cause confusion when that BIP number is actually assigned later.
On Friday, 17 July 2015, at 3:50 pm, David Barnes | Bitcoin Co. Ltd. via bitcoin-dev wrote:
> I picked up the next available number myself, but can be changed to
> anything, the 74 is unimportant to the proposal.
>
> David Barnes
>
> On 7/17/2015 2:54 PM, Micha Bailey wrote:
> > Did Greg assign this number? He didn't do it here on the ML. You're
> > not supposed to use arbitrary numbers, certainly not numbers that are
> > close/similar to ones already assigned.
> >
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2015-07-17 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 2:26 David Barnes | Bitcoin Co. Ltd.
[not found] ` <CADu7o8OAicbtXwkxbsN=joirurBKt2ta-XwMYY622pUjR+drZQ@mail.gmail.com>
2015-07-17 3:30 ` David Barnes | Bitcoin Co. Ltd.
[not found] ` <CAAmoQf113y=Xd9R+b5yS=d9yo5SAX8+Nrv3gQt-R7Jih0UBOBg@mail.gmail.com>
2015-07-17 8:50 ` David Barnes | Bitcoin Co. Ltd.
2015-07-17 12:24 ` Matt Whitlock [this message]
2015-07-17 12:40 ` David Barnes | Bitcoin Co. Ltd.
[not found] ` <CAHv+tb5B=i9FeCX-NXkTpRE_j8hwam_aWupEA_3xtBH8366sww@mail.gmail.com>
2015-07-17 15:47 ` David Barnes | Bitcoin Co. Ltd.
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=15824042.UJUZ1yd9UW@crushinator \
--to=bip@mattwhitlock$(echo .)name \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=david.barnes@bitcoin$(echo .)co.th \
/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