Skip to content

Conversation

@sipa
Copy link
Member

@sipa sipa commented Apr 3, 2015

As suggested in #5952: a script to verify that subtree contents matches upstream subtree.

@fanquake
Copy link
Member

fanquake commented Apr 5, 2015

Testing. @sipa Does this match what you'd expect to see?

bash-3.2$ contrib/devtools/git-subtree-check.sh src/secp256k1
src/secp256k1 in HEAD was last updated to upstream commit 50cc6ab0625efda6dddf1dc86c1e2671f069b0d8 (tree 3b675a638355f8ccad0474900fed0bffcda8e62a)
src/secp256k1 in HEAD currently refers to tree 3b675a638355f8ccad0474900fed0bffcda8e62a
GOOD
bash-3.2$ contrib/devtools/git-subtree-check.sh src/leveldb
src/leveldb in HEAD was last updated to upstream commit 7d41e6f89ff04ce9e6a742932924796f69c6e23d (tree ab3e90ac840140eb5bec8a5c69bf890162a43941)
src/leveldb in HEAD currently refers to tree ab3e90ac840140eb5bec8a5c69bf890162a43941
GOOD

@sipa
Copy link
Member Author

sipa commented Apr 5, 2015

You indeed expect it to say 'GOOD'.

Note that it will fail for src/secp256k1 in 0.10, as that has local modifications on top of the upstream import.

@laanwj laanwj added the Docs label Apr 8, 2015
@laanwj laanwj merged commit 5ff94c6 into bitcoin:master Apr 8, 2015
laanwj added a commit that referenced this pull request Apr 8, 2015
5ff94c6 Add git-subtree-check.sh script (Pieter Wuille)
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants