Fix copyright date #157
Merged
Fix copyright date #157
Conversation
This file contains 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
MoonkiHong
requested review from
MoonkiHong,
suresh-lc and
Karthikeyan-Samsung
|
@tdrozdovsky Thank you. Will back to you soon after our |
MoonkiHong
reviewed
Nov 2, 2020
There was a problem hiding this comment.
@tdrozdovsky Please see my comment (for a suggestion to revise)
Signed-off-by: Taras Drozdovskyi <t.drozdovsky@samsung.com>
tdrozdovsky
force-pushed
the
fix-copyright-date
branch
from
abb1da5
to
071f6ca
Compare
suresh-lc
approved these changes
Nov 4, 2020
4 tasks
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.
Signed-off-by: Taras Drozdovskyi t.drozdovsky@samsung.com
Description
The correction concerns the copyright date. Since according to the rules, after changing the file, the year of change is added and not corrected. for example the file was created in 2016, in 2019 and in 2020 was edited then the entry should be 2016, 2019-2020.
This must be strictly followed as this can lead to ownership disputes.
P.S. If you know more files where this was fixed from 2019 to 2020, please make the edits.
Type of change
Checklist: