public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Sjors Provoost <sjors@sprovoost•nl>
To: Michael Ford <fanquake@gmail•com>,
	Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Core 24.1 released
Date: Fri, 19 May 2023 13:20:26 +0200	[thread overview]
Message-ID: <D8B548F5-9330-47EE-82E1-EAD1CFE8D835@sprovoost.nl> (raw)
In-Reply-To: <CAFyhPjVNQztgy-+Jrnhcd9qS=Uky3_m4LnO1NA+2=WCc0PzoRQ@mail.gmail.com>

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

There's a typo in the tracker subdomain: trakcer.bitcoin.sprovoost.nl <http://trakcer.bitcoin.sprovoost.nl/> should be tracker.bitcoin.sprovoost.nl <http://tracker.bitcoin.sprovoost.nl/>, but I'll just add that subdomain now.

- Sjors

> Op 19 mei 2023, om 12:56 heeft Michael Ford via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> het volgende geschreven:
> 
> Bitcoin Core version 24.1 is now available from:
> 
>  <https://bitcoincore.org/bin/bitcoin-core-24.1/>
> 
> Or through BitTorrent:
> 
>  magnet:?xt=urn:btih:ebb58d7495a8aaed2f20ec4ce3e5ae27aff69529&dn=bitcoin-core-24.1&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969%2Fannounce&tr=udp%3A%2F%2Fexplodie.org%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.torrent.eu.org%3A451%2Fannounce&tr=udp%3A%2F%2Ftrakcer.bitcoin.sprovoost.nl%3A6969



[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-05-19 11:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 10:56 Michael Ford
2023-05-19 11:20 ` Sjors Provoost [this message]
2023-05-21 21:21 ` [bitcoin-dev] Full-RBF Peering Bitcoin Core v24.1 Released Peter Todd

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=D8B548F5-9330-47EE-82E1-EAD1CFE8D835@sprovoost.nl \
    --to=sjors@sprovoost$(echo .)nl \
    --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