The changes can be verified by running test/lint/git-subtree-check.sh src/ipc/libmultiprocess as described in developer notes and lint instructions.
Change since last subtree update (#35661):
max_connections parameter to ListenConnections (#269)This is needed for #35037 which lets the maximum number of IPC of incoming connections be configured in bitcoin core.
28e056576a3 Merge bitcoin-core/libmultiprocess#269: proxy: add local connection limit to ListenConnections
39a10ce8958 proxy: add local connection limit to ListenConnections()
43172f52d9e test: add dedicated ListenConnections coverage
033f8121957 doc/version: Bump version 11 > 12
git-subtree-dir: src/ipc/libmultiprocess
git-subtree-split: 28e056576a309b76bf5885bc1d1c89c7191602b9
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/35684.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline and AI policy for information on the review process. A summary of reviews will appear here.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
Possible typos and grammar issues:
first accepts clients disconnects -> first accepted client disconnects [the current wording is grammatically broken and obscures the intended meaning]<sup>2026-07-08 15:44:05</sup>
(deleted my initial review, needed to double check)
I still get confused on how to check for backport support, it would be better if the subtree linter printed something about that.
git show HEAD^2^1^1^1 follows the trail of squash commits through previous subtree updates, so that's good.
But shouldn't the merge commit HEAD^1 point to 02afa66169b5dc58d0fc6f608d0c6f4facefd5ec instead of 32941e131479b4aec1eb606d68a9bcc3f5d7cf3d?