From: John Tromp <john.tromp@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] What to do when contentious soft fork activations are attempted
Date: Fri, 6 May 2022 21:58:44 +0200 [thread overview]
Message-ID: <CAOU__fwuT8tuV+5KG28toxQO1kwgm0S7CHtsQrZqx7my9RwCtQ@mail.gmail.com> (raw)
In-Reply-To: <mailman.53264.1651860071.8511.bitcoin-dev@lists.linuxfoundation.org>
On Fri, 6 May 2022 7:17PM Jorge Tim?n wrote
> But let's not personally attack andreas for his opinions.
> The only reason you don't like bip8 is because you're ignorant about it and
> you haven't reviewed it enough.
Can you see the irony in equating "clueless about BIP119" with a
personal attack and then calling Jeremy ignorant about BIP8?
-John
next parent reply other threads:[~2022-05-06 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.53264.1651860071.8511.bitcoin-dev@lists.linuxfoundation.org>
2022-05-06 19:58 ` John Tromp [this message]
2022-05-07 1:57 ` Jorge Timón
2022-04-30 9:53 Michael Folkson
2022-05-01 1:20 ` alicexbt
2022-05-01 12:47 ` Jorge Timón
2022-05-03 14:36 ` Ryan Grant
2022-05-06 17:17 ` Jorge Timón
2022-05-06 18:23 ` Russell O'Connor
2022-05-06 22:44 ` Jorge Timón
2022-05-01 19:14 ` Billy Tetrud
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=CAOU__fwuT8tuV+5KG28toxQO1kwgm0S7CHtsQrZqx7my9RwCtQ@mail.gmail.com \
--to=john.tromp@gmail$(echo .)com \
--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