From: Bryan Bishop <kanzure@gmail•com>
To: Luke Dashjr <luke@dashjr•org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Bryan Bishop <kanzure@gmail•com>
Subject: Re: [bitcoin-dev] Revising BIP 2 to expand editorial authority
Date: Wed, 27 Sep 2017 14:01:40 -0500 [thread overview]
Message-ID: <CABaSBaz=pMfTz2UF-WpyxrkGY9XZO+zTHR7-Oie79J1Ap10hpQ@mail.gmail.com> (raw)
In-Reply-To: <201709271856.27376.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On Wed, Sep 27, 2017 at 1:56 PM, Luke Dashjr via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> 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.
>
Even minor revisions can not change the meaning of text. Changing a single
word can often have a strange impact on the meaning of the text. There
should be some amount of care exercised here. Maybe it would be okay as
long as edits are mentioned in the changelog at the bottom of each
document, or mention that the primary authors have not reviewed suggested
changes, or something as much; otherwise the reader might not be aware to
check revision history to see what's going on.
- Bryan
http://heybryan.org/
1 512 203 0507
[-- Attachment #2: Type: text/html, Size: 1372 bytes --]
next prev parent reply other threads:[~2017-09-27 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 18:56 Luke Dashjr
2017-09-27 19:01 ` Bryan Bishop [this message]
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='CABaSBaz=pMfTz2UF-WpyxrkGY9XZO+zTHR7-Oie79J1Ap10hpQ@mail.gmail.com' \
--to=kanzure@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(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