What the developer wrote
Authored by Sjors Provoost
doc: how to update a subtree
What changed, and why it matters
This commit only adds documentation explaining how developers can update a code subtree (a bundled external library). It contains no code changes, no configuration changes, and no security fixes or functional behavior changes.
No security action needed. This is a documentation-only commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds 13 lines to doc/developer-notes.md with shell examples for adding a Git remote and running git subtree pull for the libmultiprocess subtree. It is purely procedural developer documentation.
Changed components
doc/developer-notes.mdInspect captured patch +13 / −0
diff --git a/doc/developer-notes.md b/doc/developer-notes.md
index 220343ab..1617662a 100644
--- a/doc/developer-notes.md
+++ b/doc/developer-notes.md
@@ -1119,6 +1119,19 @@ to check a subtree directory for consistency with its upstream repository.
The tool instructions also include a list of the subtrees managed by Bitcoin Core.
+To fully verify or update a subtree, add it as a remote:
+
+```sh
+git remote add libmultiprocess https://github.com/bitcoin-core/libmultiprocess.git
+```
+
+To update the subtree:
+
+```sh
+git fetch libmultiprocess
+git subtree pull --prefix=src/ipc/libmultiprocess libmultiprocess master --squash
+```
+
The ultimate upstream of the few externally managed subtrees are:
- src/leveldb
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.