aboutsummaryrefslogtreecommitdiff
path: root/src/m4
diff options
context:
space:
mode:
authorfanquake <fanquake@gmail.com>2023-04-19 09:05:41 +0100
committerfanquake <fanquake@gmail.com>2023-04-19 09:19:49 +0100
commit36c15d7d5cf6035bf76e54b88364373671e86337 (patch)
tree30845369dce10d3438aa54c85594685c0b3a44b2 /src/m4
parent15a24781d01847d3acb77607148eae1c05cd5d4f (diff)
parent03a16a1da09f45721c799c719e48350dfe12ae88 (diff)
Merge bitcoin/bitcoin#27486: [24.1] Bump version to 24.1rc2v24.1rc2
03a16a1da09f45721c799c719e48350dfe12ae88 doc: update release notes for 24.1rc2 (fanquake) f344c66053f1f1c24c0dac3ecc9570bea5c7fa0a doc: update manual pages for v24.1rc2 (fanquake) 4451e899881f2ae6b46c13ff87618d45a6fa982f build: bump version to v24.1rc2 (fanquake) Pull request description: rc1 (tagged > a month ago) was mostly a no-op, due to lack of binaries. While some are up now, [albeit at the wrong URL](https://bitcoincore.org/bin/bitcoin-24.1rc1/), there seems no point continuing the rc1 cycle, when we already have additional changes backported (#27474), and we've also received no bug reports/feedback from anyone who did test. So bump the version, and cut an rc2. ACKs for top commit: achow101: ACK 03a16a1da09f45721c799c719e48350dfe12ae88 gruve-p: ACK https://github.com/bitcoin/bitcoin/pull/27486/commits/03a16a1da09f45721c799c719e48350dfe12ae88 hebasto: ACK 03a16a1da09f45721c799c719e48350dfe12ae88, I have reviewed the code and it looks OK. Tree-SHA512: f49072149ecabb02b034b1c4d7319a80f93a8c7a29a2b7ec27dff0c257742d08d48fbf266399ce71769cec992902b7d53fc26bb5ffc8681728dc8685cbba25d9
Diffstat (limited to 'src/m4')
0 files changed, 0 insertions, 0 deletions