Bump © to 2026; Add repo LICENSE; Strip file-level headers#136
Open
imnasnainaec wants to merge 3 commits into
Open
Bump © to 2026; Add repo LICENSE; Strip file-level headers#136imnasnainaec wants to merge 3 commits into
imnasnainaec wants to merge 3 commits into
Conversation
Contributor
|
I don't usually bump up version numbers across all source files wholesale. It don't know that it hurts anything, but unless the file has actually changed, in what sense does its copyright date need to be updated? |
Collaborator
Author
I'd be in favor of removing the file-level copyrights. But as long as they're there, I figure might as well update all to account for all recent changes. |
Contributor
👍👍👍 In my opinion, they are worthless and just cause this kind of unnecessary churn. |
dab7f59 to
0e19d87
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change is