From: Btc Drak <btcdrak@gmail•com>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposed minor change to BIP 01 to use a PR for request assignment
Date: Fri, 4 Sep 2015 00:45:13 +0100 [thread overview]
Message-ID: <CADJgMzvQ2g7Sr3w3_iDCY4WhZ3RuMWdmYOwib6+b4FSbB5LguA@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgR4iGshOgsammWQ93yD0GsckUgroX-sb7mDE7XuQb5k3g@mail.gmail.com>
It's a good idea. It would remove friction from the process and
assignment is auditable to boot, something I've had difficulty with in
the past. Almost every time I see a BIP number I would wonder, is that
self-assigned (and thus invalid) or has it been assigned by the BIP
editor.
On Fri, Sep 4, 2015 at 12:18 AM, Gregory Maxwell via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> 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!)
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2015-09-03 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 23:18 Gregory Maxwell
2015-09-03 23:45 ` Btc Drak [this message]
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=CADJgMzvQ2g7Sr3w3_iDCY4WhZ3RuMWdmYOwib6+b4FSbB5LguA@mail.gmail.com \
--to=btcdrak@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gmaxwell@gmail$(echo .)com \
/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