Update shading_language_selection.cpp

[RobertHenry6bev]

Fix typo in a LOGI message

Description

Fix typo

I have done no testing. I only see this typo in one place.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ SaschaWillems
❌ RobertHenry6bev
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[SaschaWillems]

@RobertHenry6bev This fails at CI. You need to update the copyright of the file(s) you changed.

[marty-johnson59]

Hi @RobertHenry6bev, it looks like you need to sign the CLA before we can merge this. LMK if questions on how to do that. Thanks.

[RobertHenry6bev]

As far as I remember, I have never done this before. (The overhead is a little high for a small change, but, ok).

So I vist https://cla-assistant.io/my-cla and after granting the assistant all the permissions it asks for, am led to a web page that says (with my hand edits to insert table col separators '|':

Status Repository CLA Date of Signature
OK | KhronosGroup / Vulkan-Samples | Khronos Open Source Contributor License Agreement | January 15, 2025

Is this sufficient?
You have my permission to make the changes yourself. I was merely trying to be a good citizen to fix something my "proofreader's eye" caught.
I recently retired from 40 years in CS/engineering, and so do not have to bow to my corporate lawyers.

[marty-johnson59]

Thanks. Yah, does seem like overkill for such a small change, but the tools are strict on licensing around here.. Looks like there's a merge conflict now (hopefully easy to resolve?). If this is too much of a pain, just LMK - we're happy to do this tweak ourselves too:)

[RobertHenry6bev]

Yah, this is too much of a pain for me right now. I would appreciate it if you closed this PR and then applied the changes yourself. Thank you very much!

[marty-johnson59]

Sounds good. We'll take care of it. Thanks for pointing this out to us - very much appreciate the help!

[asuessenbach]

I think, with #1304, this PR is obsolete.

[SaschaWillems]

Yes, that's correct. I did copy the spelling error and just fixed it a long the way ;)