aboutsummaryrefslogtreecommitdiff
path: root/test/functional/p2p_invalid_messages.py
diff options
context:
space:
mode:
authorMarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz>2022-12-06 16:53:54 +0100
committerMarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz>2022-12-06 16:54:10 +0100
commitb3f866a8dfd652b6339b79124843e58bd0bf3013 (patch)
tree2ad556b61a48e1afb76c95b967ce7dcc31d3529c /test/functional/p2p_invalid_messages.py
parent3afbc7d67d8e6225db73cbd298bcf738df11f03a (diff)
parenta9ea7158351ad89f62a13335368df8cc54114f7f (diff)
Merge bitcoin/bitcoin#26647: 24.0.1 final changesv24.0.1
a9ea7158351ad89f62a13335368df8cc54114f7f doc: adjust release notes for 24.0.1 (fanquake) c119b0a1766d2b3daa07c09da7947afe862f4bd1 doc: generate manual pages for 24.0.1 final (fanquake) 1b19c894a2c282177335fd61f633d4d6fd38d425 build: bump version to 24.0.1 final (fanquake) Pull request description: Changes for 24.0.1. At this stage, I don't think an rc is necessary here, and would just add another 5-x days delay to fixing these issues. This will be accompanied by a pull request to master to add a note in the 24.0.md that already exists there. Similar to what was done with 0.19.0.1. ACKs for top commit: gruve-p: ACK https://github.com/bitcoin/bitcoin/pull/26647/commits/a9ea7158351ad89f62a13335368df8cc54114f7f instagibbs: ACK https://github.com/bitcoin/bitcoin/pull/26647/commits/a9ea7158351ad89f62a13335368df8cc54114f7f hebasto: ACK a9ea7158351ad89f62a13335368df8cc54114f7f, I have reviewed the changes and they look OK. josibake: ACK https://github.com/bitcoin/bitcoin/pull/26647/commits/a9ea7158351ad89f62a13335368df8cc54114f7f w0xlt: ACK https://github.com/bitcoin/bitcoin/pull/26647/commits/a9ea7158351ad89f62a13335368df8cc54114f7f Tree-SHA512: 2e0d81ef91d947c9d55dcadcb6168fbb5251a5e613642c6250075add6a4f14f54cbb452934fa46aec035decb339e611fe721f5e9d9156e47a0341c3be26f5aa9
Diffstat (limited to 'test/functional/p2p_invalid_messages.py')
0 files changed, 0 insertions, 0 deletions