scripted-diff: Remove copyright year (ranges) #179

pull maflcko wants to merge 1 commits into bitcoin-core:master from maflcko:2506-doc-fixup changing 50 files +50 −50
  1. maflcko commented at 9:59 am on June 2, 2025: contributor

    The years are problematic, because they can mean different things to different people, they are not needed, inconsistent and redundant.

    So just remove them with a scripted-diff, which can be checked via a script from the Bitcoin Core repo: ../bitcoin-core/test/lint/commit-script-check.sh HEAD~..HEAD

    To give some more context:

    • Anyone who wants to find the initial file creation date, or file history, can use git log or git blame to get more accurate results.
    • Some files use stale ranges (src/mp/util.cpp), others do not, so it is unclear if ranges need to be added or updated, and when.

    So just remove the years (or ranges) in this project with an easy scripted-diff.

  2. scripted-diff: Remove copyright year (ranges)
    -BEGIN VERIFY SCRIPT-
     sed -i --regexp-extended 's;( 20[0-2][0-9])(-20[0-2][0-9])? The Bitcoin Core developers; The Bitcoin Core developers;g' $( git grep -l 'The Bitcoin Core developers' -- ':(exclude)COPYING' )
    -END VERIFY SCRIPT-
    fa2ff9a668
  3. ryanofsky commented at 8:14 pm on June 11, 2025: collaborator

    Code review ACK fa2ff9a66842c094060bd90ddf61232e078e4072. Makes sense to get rid of these instead of bumping them.

    they can mean different things to different people

    I don’t get how there are multiple ways to interpret the dates. Copyright lasts for a period of time and the dates tell you when the period begins. If there’s a range or list of dates, the older dates tell when you older parts of the file will enter public domain, and the latest date tells you when the whole file will. Since the dates are only accurate if we bump them periodically, or whenever editing, and it would be annoying to do this, it’s nice to drop them. But I don’t think they were ambiguous, just wrong.

  4. ryanofsky merged this on Jun 11, 2025
  5. ryanofsky closed this on Jun 11, 2025

  6. maflcko deleted the branch on Jun 12, 2025
  7. ryanofsky referenced this in commit 07dda23f6b on Jun 13, 2025
  8. ryanofsky referenced this in commit 5bf57b1ea2 on Jun 16, 2025
  9. ryanofsky referenced this in commit e0e4d3bd05 on Jun 16, 2025
  10. Sjors referenced this in commit ebfb66188e on Jun 24, 2025
  11. ryanofsky referenced this in commit 9b4ec43f78 on Jun 24, 2025
  12. Sjors referenced this in commit 063587c2de on Jun 27, 2025
  13. ryanofsky referenced this in commit 96bcbb60a6 on Jul 1, 2025
  14. ryanofsky referenced this in commit 6e40719c06 on Jul 1, 2025
  15. ryanofsky referenced this in commit ca509dd2b9 on Jul 1, 2025
  16. ryanofsky referenced this in commit e886c65b6b on Aug 8, 2025
  17. Sjors referenced this in commit 8ce8288ee6 on Aug 12, 2025
  18. fanquake referenced this in commit f58de8749e on Aug 18, 2025
  19. janus referenced this in commit d7ab135840 on Sep 15, 2025

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin-core/libmultiprocess. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2025-12-04 19:30 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me