From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Revising BIP 2 to expand editorial authority
Date: Wed, 27 Sep 2017 18:56:26 +0000 [thread overview]
Message-ID: <201709271856.27376.luke@dashjr.org> (raw)
Many pull requests to the BIPs repository are spelling corrections or similar,
which are obvious to merge. Currently, the BIP process requires the Author of
the affected BIPs to ACK any changes, which seems inefficient and unnecessary
for these kind of editorial fixes.
What do people think about modifying BIP 2 to allow editors to merge these
kinds of changes without involving the Authors? Strictly speaking, BIP 2
shouldn't be changed now that it is Active, but for such a minor revision, I
think an exception is reasonable.
I've prepared a draft PR for BIP 2 here:
https://github.com/bitcoin/bips/pull/596
If you oppose this change, please say so within the next month.
Luke
next reply other threads:[~2017-09-27 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 18:56 Luke Dashjr [this message]
2017-09-27 19:01 ` Bryan Bishop
2017-09-27 20:20 ` Sjors Provoost
2017-09-27 21:00 ` Jean-Paul Kogelman
2017-09-28 12:43 ` Christian Decker
2017-09-29 1:52 ` 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=201709271856.27376.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--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