To avoid a common newbie mistake like the pull request rejected #3944, adding a simple instruction to the documentation Coding Convention of Bitcoin Core (doc/coding.md). The actual author of this short text (slightly modified) is Gavin Andresen sent by email to me as a tip.
Related:
To avoid a common newbie mistake like the pull request rejected #3944, adding a simple instruction to the documentation Coding Convention of Bitcoin Core (doc/coding.md). The actual author of this short text (slightly modified) is Gavin Andresen sent by email to me as a tip.
Related:
- https://github.com/bitcoin/bitcoin/pull/3944#issuecomment-38467282
- https://github.com/bitcoin/bitcoin/pull/3646
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/b6b4809f81ffde540036c8883dac03032ecb684d for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
I'd stop at "Resist the urge to fix copyright years in all the files in the source tree.".
There is no contrib/devtools/fix_copyright_headers.py script, and I also don't really want to encourage new developers to run scripts that do all-over-the-source changes.
I'm sorry, you are right. The right is fix-copyright-headers.py and not fix_copyright_headers.py. Just my mistake in a wrong copy/past. Thank you.