From: yancy <email@yancy.lol>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Taproot Activation Meeting 4/20 Cancelled
Date: Sat, 17 Apr 2021 20:10:39 +0000 (UTC) [thread overview]
Message-ID: <bbba02b6-a041-4d7c-b58c-4f7f0f4100ca@yancy.lol> (raw)
In-Reply-To: <CAD5xwhi_ymtyu_A9Whm-8i8XPB=ZWZZZrm79PN+vfhsnUPPSkg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 102 bytes --]
I appreciate the bluntness, Jeremy, and agree it's high time folks enjoy the holiday.
Cheers,
-Yancy
[-- Attachment #2: Type: text/html, Size: 315 bytes --]
prev parent reply other threads:[~2021-04-17 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 18:45 [bitcoin-dev] Taproot Activation Meeting 4/20 Cancelled Jeremy
2021-04-17 20:10 ` yancy [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=bbba02b6-a041-4d7c-b58c-4f7f0f4100ca@yancy.lol \
--to=email@yancy.lol \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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