From: Matt Corallo <lf-lists@mattcorallo•com>
To: Luke Dashjr <luke@dashjr•org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Reminder on the Purpose of BIPs
Date: Sun, 25 Apr 2021 17:31:50 -0400 [thread overview]
Message-ID: <248f871e-1b83-8c7c-678b-3ed0585a6357@mattcorallo.com> (raw)
In-Reply-To: <202104252122.40909.luke@dashjr.org>
Alright, let's see...
Sorting by most recently updated...
https://github.com/bitcoin/bips/pulls?page=1&q=is%3Apr+is%3Aopen+sort%3Aupdated-asc+updated%3A%3E2021-01-01
#1104 has been updated nearly daily for the past many weeks. You commented 12 days ago saying "Concept NACK" (which
isn't a thing on BIPs - huh? they're author documents, as you're well aware), and nothing further.
#1105 which is less recently updated by one on the above list has a comment from you 19 hours ago.
I'm really not sure what playing dumb gets you, here. Its really transparent and isn't helpful in any way to anything.
In general, I think its time we all agree the BIP process has simply failed and move on. Luckily its not really all that
critical and proposed protocol documents can be placed nearly anywhere with the same effect.
Matt
On 4/25/21 17:22, Luke Dashjr wrote:
> On Sunday 25 April 2021 21:14:08 Matt Corallo wrote:
>> On 4/25/21 17:00, Luke Dashjr wrote:
>>> I will not become an accomplice to this deception by giving special
>>> treatment, and will process the BIP PR neutrally according to the
>>> currently-defined BIP process.
>>
>> Again, please don't play dumb, no one watching believes this - you've been
>> active on the BIP repo on numerous PRs and this has never in the past been
>> the case.
>
> I started going through PRs a few days ago, in order of "Recently updated" on
> GitHub, starting with the least-recent following the last one I triaged a
> month ago that hasn't seen activity.. the same as I have been doing month
> after month prior to this.
>
> If you don't believe me, feel free to look through the repo history.
>
> Luke
>
next prev parent reply other threads:[~2021-04-25 21:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 2:09 [bitcoin-dev] Proposed BIP editor: Kalle Alm Luke Dashjr
2021-04-23 3:36 ` Jeremy
2021-04-23 7:49 ` John Newbery
2021-04-23 7:50 ` Pindar Wong
2021-04-23 9:11 ` Eric Martindale
2021-04-23 15:34 ` Antoine Riard
2021-04-24 10:16 ` nopara73
2021-04-25 20:29 ` [bitcoin-dev] Reminder on the Purpose of BIPs Matt Corallo
2021-04-25 21:00 ` Luke Dashjr
2021-04-25 21:14 ` Matt Corallo
2021-04-25 21:22 ` Luke Dashjr
2021-04-25 21:31 ` Matt Corallo [this message]
2021-04-26 19:43 ` David A. Harding
2021-04-26 20:04 ` Greg Maxwell
2021-04-27 19:43 ` Melvin Carvalho
2021-04-27 9:04 ` W. J. van der Laan
2021-04-27 11:49 ` Erik Aronesty
2021-04-27 11:33 ` John Newbery
2021-04-27 12:16 ` Jorge Timón
2021-04-26 15:02 ` [bitcoin-dev] Proposed BIP editor: Kalle Alm Sjors Provoost
2021-04-26 16:56 ` James O'Beirne
2021-04-26 18:13 ` W. J. van der Laan
2021-09-15 9:50 [bitcoin-dev] Reminder on the Purpose of BIPs Prayank
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=248f871e-1b83-8c7c-678b-3ed0585a6357@mattcorallo.com \
--to=lf-lists@mattcorallo$(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