Some trivial maintenance to avoid having to do it again after the 0.17 branch off.
(The scripts to do this are in ./contrib/)
Some trivial maintenance to avoid having to do it again after the 0.17 branch off.
(The scripts to do this are in ./contrib/)
<!--e57a25ab6845829454e8d69fc972939a-->Note to reviewers: This pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
22 | @@ -23,7 +23,7 @@ 23 | 24 | static const uint64_t GB_BYTES = 1000000000LL; 25 | /* Minimum free space (in GB) needed for data directory */ 26 | -static const uint64_t BLOCK_CHAIN_SIZE = 200; 27 | +constexpr uint64_t BLOCK_CHAIN_SIZE = 220;
static?
Is it possible for a constexpr to be non-static?
Can the copyright headers be a scripted diff?
Why do we have generated manpages in the repo? (maybe not the right time to address that)
@Sjors They can't since the script takes into account the current time to determine what to bump to. So you coulnd't verify the scripted diff without setting the time to the commit time.
What if you could pass YEAR=2018 into the script, or if the year is committed first?
@Sjors Jup, that'd work. Though, I feel we should do that in a separate pull request.
@MarcoFalke that's fine, this is easy enough to review. Is this ready for review or are you planing to add more?
I am not aware of anything else that needs to be done pre-branch
ACK 3fc2063
utACK 3fc2063
utACK 3fc20632a3ad30809356a58d2cf0ea4a4ad4cec3
@laanwj They'd have to be bumped every time the version is bumped on the 0.17 branch anyway. So imo it can be done later to not invalidate the review here.
OK I thought the idea was to generate these just before the branch, but otherwise is ok me too.