Closed
Conversation
Author
|
Hi @srbaeza-ai, thanks for the added context. Clarifying for other readers, that link is to the initial commit for the dotnet runtime repository (dated Nov, 2019) where the MIT license file (which does not contain a date in the copyright) was first added to the repository. |
Contributor
|
Hmm I think I read this PR and was thinking of it when replying on #1304 (comment) ... so actually, thank you @swharden for raising the question. I removed the copyright year. |
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.
Commits to this repository have been made in 2024, but present copyright date range ends at 2023. This PR updates the date range to include the current year.
Should the copyright date range be removed to prevent this file requiring yearly modification in the future?