Bitcoin Development Mailinglist
 help / color / mirror / Atom feed
From: Bryan Bishop <kanzure@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Cc: Bryan Bishop <kanzure@gmail.com>
Subject: Re: [bitcoindev] Motion to remove Luke Dashjr from BIP Editors
Date: Mon, 10 Aug 2026 15:51:29 -0500	[thread overview]
Message-ID: <CABaSBaxXsU6rB98aYh8p+T3_Gsuj=VU7MoKuDFWrqoBE-Oqp1w@mail.gmail.com> (raw)
In-Reply-To: <ad36522e-f479-4ac3-9904-cf00cfa8ec46@murch.one>

[-- Attachment #1: Type: text/plain, Size: 683 bytes --]

On Sun, Aug 9, 2026 at 1:53 PM Murch <murch@murch.one> wrote:

> I recommend that Luke Dashjr be removed from the position of BIP Editor.
>

The individual known as Luke Dashjr is no longer a permissioned user on the
BIP content repository.

- Bryan
https://x.com/kanzure

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CABaSBaxXsU6rB98aYh8p%2BT3_Gsuj%3DVU7MoKuDFWrqoBE-Oqp1w%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 1379 bytes --]

      parent reply	other threads:[~2026-08-10 20:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-09 18:29 [bitcoindev] Motion to remove Luke Dashjr from BIP Editors Murch
2026-08-09 19:35 ` Luke Dashjr
2026-08-10 15:20   ` Murch
2026-08-09 19:47 ` Jameson Lopp
2026-08-09 19:48 ` Matt Corallo
2026-08-09 20:42   ` Michael Tidwell
2026-08-10  1:40     ` Antoine Riard
2026-08-09 20:56 ` Olaoluwa Osuntokun
2026-08-10  8:08 ` Jonas Nick
2026-08-10 15:05 ` Anthony Towns
2026-08-10 15:30 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2026-08-10 20:51 ` Bryan Bishop [this message]

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='CABaSBaxXsU6rB98aYh8p+T3_Gsuj=VU7MoKuDFWrqoBE-Oqp1w@mail.gmail.com' \
    --to=kanzure@gmail.com \
    --cc=bitcoindev@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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