-
-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated copyright blocks #2866
Updated copyright blocks #2866
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
love it
just, why? |
If I remember correctly the script created by @justinbeaty makes changes only in the files that have been changed in the meantime. There is a long discussion why we need to change the copyright header in a few places (#2276, #2297) and here for legal aspects (#2295). |
@Flyingmana we started this with #2297. Now we can/could/should keep it up to date? Are there any downsides? |
the downsides are documented in a decade of people complaining about Magento doing this, because it makes creating diffs a lot harder. on the other side iam not convinced of any of the Advantages. |
in the old times they were updating every single file at every release. we're just updating the files that were actually modified, which makes 78% more sense ;-) |
82% ... at least. |
Changing the header can also be seen as useful information. For example, a file had its last changes in the year 2022. Not that it would help much, but there are files that we have never touched inherited from Magento. |
This reverts commit c8ecedd.
Description (*)
I took me some hours to go though all files that changes and updated copyright blocks .... not.
Just used #2295 👍
Contribution checklist (*)