Skip to content

Update Arm copyrights to 2022#758

Merged
kpet merged 1 commit intoKhronosGroup:masterfrom
alycm:copyright-2022-arm
Feb 14, 2022
Merged

Update Arm copyrights to 2022#758
kpet merged 1 commit intoKhronosGroup:masterfrom
alycm:copyright-2022-arm

Conversation

@alycm
Copy link
Copy Markdown
Contributor

@alycm alycm commented Feb 14, 2022

One file listed both a Khronos Group and Arm copyright, as this is a vendor
extension I assumed that Arm was the correct choice. No other vendor extension
has a copyright comment, just the copyright in the text, so I just deleted the
Khronos Group lines.

One file listed both a Khronos Group and Arm copyright, as this is a vendor
extension I assumed that Arm was the correct choice.  No other vendor extension
has a copyright comment, just the copyright in the text, so I just deleted the
Khronos Group lines.
@alycm alycm requested a review from kpet February 14, 2022 00:18
Copy link
Copy Markdown
Contributor

@kpet kpet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. What prompted this change?

@alycm
Copy link
Copy Markdown
Contributor Author

alycm commented Feb 14, 2022

@kpet As far as I know it is standard practice in Khronos repo's to just mass-update the copyright dates, e.g. as recently done by Vulkan and OpenXR.

I'm not really sure if it serves much purpose, or has advantages over excluding the date, but to be honest just doing the formulaic update is less work than thinking about that!

@kpet
Copy link
Copy Markdown
Contributor

kpet commented Feb 14, 2022

Right, that was my guess. Agree it's not worth spending too much time discussing the relative merits of all options :). Thanks for doing this! I'll merge this one since it's Arm-only and very straightforward.

@kpet kpet merged commit 4866e33 into KhronosGroup:master Feb 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants