From: Peter Todd <pete@petertodd•org>
To: Michael Ford <fanquake@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Core 24.0.1 Released
Date: Tue, 13 Dec 2022 16:17:21 -0500 [thread overview]
Message-ID: <Y5jr4UMPza/Rp9zb@petertodd.org> (raw)
In-Reply-To: <CAFyhPjWjcLRo6WDzOT+dGSYwq-68gMh-O4hw1O470kanbrq-=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
On Tue, Dec 13, 2022 at 12:06:47PM +0000, Michael Ford via bitcoin-dev wrote:
> Due to last-minute issues (https://github.com/bitcoin/bitcoin/pull/26616),
> 24.0, although tagged, was never fully announced or released.
>
> Bitcoin Core version 24.0.1 is now available from:
>
> https://bitcoincore.org/bin/bitcoin-core-24.0.1/
Note that the PGP signature on this email is bad:
[-- PGP output follows (current time: Tue 13 Dec 2022 04:15:30 PM EST) --]
gpg: WARNING: no command supplied. Trying to guess what you mean ...
gpg: Signature made Tue 13 Dec 2022 07:06:06 AM EST
gpg: using RSA key CFB16E21C950F67FA95E558F2EEB9F5CC09526C1
gpg: BAD signature from "Michael Ford (bitcoin-otc) <fanquake@gmail•com>" [full]
[-- End of PGP output --]
[-- BEGIN PGP SIGNED MESSAGE --]
Due to last-minute issues (https://github.com/bitcoin/bitcoin/pull/26616),
24.0, although tagged, was never fully announced or released.
The announcement on bitcoin-core-dev was had an invalid signature.
Likely some formatting error - your mail client also send it as text and html
at the same time. No-one should be sending html emails to this mailing list.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-13 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 12:06 Michael Ford
2022-12-13 21:17 ` Peter Todd [this message]
2022-12-13 21:28 ` Matt Corallo
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=Y5jr4UMPza/Rp9zb@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=fanquake@gmail$(echo .)com \
/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