doc: update copyright year #1976
Merged
Conversation
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
Signed-off-by: Unai Martinez-Corral <[email protected]>
|
We can put a starting date of 2012. There was documentation before that (for vpr, then vtr, ...) but 2012 is when the first vtr paper came out so let's align with that. |
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.
Description
The year shown at the footer of the docs is
2016. This PR updates it to2012-2022. @vaughnbetz what should be the proper starting year?Related Issue
None
Motivation and Context
The docs have been updated since 2016...
How Has This Been Tested?
It's changing the content of a hardcoded string. There is no functionality change at all. It's tested in CI.
Types of changes
Checklist: