public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Cc: Prayank <prayank@tutanota.de>
Subject: Re: [bitcoin-dev] Stumbling into a contentious soft fork activation attempt
Date: Mon, 21 Feb 2022 09:11:11 +0000	[thread overview]
Message-ID: <rRR795KfaeLEPouMngjFqbITNr48YIIUgiq6TPWoseXNcOmUjJN0jLPGX88Vtmr59vwCmSgCvntjJH7UPwR2UK6e7KWkobcTKLBvzHfgqXw=@protonmail.com> (raw)
In-Reply-To: <guj6poK6x0q2u4ku4nmy_rhAsu33nSIyakg5-_NgAUMAOohUUjwaCgCgjHbcUqzx7Fym8AT6EsQginr9YjglDnwRpQTQwiG0sVQadp7_zhI=@protonmail.com>




> Good morning Prayank,
>
> (offlist)

<facepalm>

My apologies.
I pushed the wrong button, I should have pressed "Reply" and not "Reply All".

Regards,
ZmnSCPxj


  reply	other threads:[~2022-02-21  9:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18  1:57 [bitcoin-dev] Stumbling into a contentious soft fork activation attempt Prayank
2022-02-18 23:41 ` Peter Todd
2022-02-20 18:35   ` Erik Aronesty
2022-02-21  3:03     ` Prayank
2022-02-21  9:02       ` ZmnSCPxj
2022-02-21  9:11         ` ZmnSCPxj [this message]
2022-02-21  9:48         ` Prayank
2022-02-22 12:57           ` Billy Tetrud
2022-02-21  9:09       ` ZmnSCPxj
  -- strict thread matches above, loose matches on Subject: below --
2022-01-04 11:53 Prayank
2022-01-04 14:15 ` Michael Folkson
2022-01-04 15:06   ` Prayank
2022-01-04 16:48     ` Michael Folkson
2022-01-04 17:07       ` Prayank
2022-01-04 14:42 ` Christian Decker
2022-01-04 15:45   ` Prayank
2022-01-03  2:05 Michael Folkson
2022-01-09 11:38 ` Peter Todd
2022-01-11  3:42   ` Jeremy
2022-01-11  4:38     ` Jeremy

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='rRR795KfaeLEPouMngjFqbITNr48YIIUgiq6TPWoseXNcOmUjJN0jLPGX88Vtmr59vwCmSgCvntjJH7UPwR2UK6e7KWkobcTKLBvzHfgqXw=@protonmail.com' \
    --to=zmnscpxj@protonmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=prayank@tutanota.de \
    /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