From: Gregory Maxwell <gmaxwell@gmail•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Proposed minor change to BIP 01 to use a PR for request assignment
Date: Thu, 3 Sep 2015 23:18:08 +0000 [thread overview]
Message-ID: <CAAS2fgR4iGshOgsammWQ93yD0GsckUgroX-sb7mDE7XuQb5k3g@mail.gmail.com> (raw)
The process in BIP01 was written when we used a different solution for
storing and presenting BIPs.
I'm thinking of suggesting that the number request process be changed
to opening a pull req with BIP text with no number (e.g. just using
the authors name and an index as the number) as the mechenism to
request number assignment.
Is there any reason that anyone would find this objectionable?
(Please do not respond to this message with anything but a strictly
directed answer to that question, start a new thread for a different
subject. Thanks!)
next reply other threads:[~2015-09-03 23:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 23:18 Gregory Maxwell [this message]
2015-09-03 23:45 ` Btc Drak
2015-09-04 0:17 ` Marco Pontello
2015-09-04 0:24 ` Gregory Maxwell
2015-09-04 15:24 ` Peter Todd
2015-09-04 15:33 ` Douglas Roark
2015-09-04 18:41 ` Eric Lombrozo
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=CAAS2fgR4iGshOgsammWQ93yD0GsckUgroX-sb7mDE7XuQb5k3g@mail.gmail.com \
--to=gmaxwell@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