Running git-subtree-check.sh requires adding the subtree repository as a remote. I learned that several years ago and then forgot again.
This PR also improves the error message if the subtree commit can't be found.
Running git-subtree-check.sh requires adding the subtree repository as a remote. I learned that several years ago and then forgot again.
This PR also improves the error message if the subtree commit can't be found.
22 | @@ -23,6 +23,12 @@ maintained: 23 | * for `src/crypto/ctaes`: https://github.com/bitcoin-core/ctaes.git (branch master) 24 | * for `src/crc32c`: https://github.com/google/crc32c.git (branch master) 25 | 26 | +To do so, add the upstream repository as remote: 27 | + 28 | +``` 29 | +git remote add -f secp256k1 https://github.com/bitcoin-core/secp256k1.git
I wish -f was called --fetch instead
Changed.
Oh, I didn't know --fetch existed. git help remote doesn't mention it, but it seems to work, so :man_shrugging:
It does does show up when you do git remote add
ACK a4a3fc4cd2e6f53cdffcc2962fd152a4e40c7413 - this looks ok.
ACK a4a3fc4cd2e6f53cdffcc2962fd152a4e40c7413