Skip to content
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

Cherry pick PR #969: [XB1] expand resolution of VP9 playback to 4K on Xbox One X #975

Merged
merged 1 commit into from
Aug 21, 2023

Conversation

cobalt-github-releaser-bot
Copy link
Collaborator

"Refer to the original PR: #969"

@google-cla
Copy link

google-cla bot commented Jul 19, 2023

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@TyHolc
Copy link
Contributor

TyHolc commented Jul 31, 2023

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@victorpasoshnikov Can you address this? I'm not sure why it still has an issue.

@TyHolc TyHolc force-pushed the 24.lts.1+-969 branch 2 times, most recently from f79b8ea to 84ab02a Compare August 1, 2023 00:01
* [XB1] expand resolution of VP9 playback to 4K on Xbox One X

b/170479042

Change-Id: Ida305cace612077f875be7b8e20b40cbcd784aa2

* [XB1] expand resolution of VP9 playback to 4K on Xbox One X

b/170479042

Change-Id: I2def4a42522c796cafd91c500b1e59ef8882925b
(cherry picked from commit fb789f2)
@TyHolc
Copy link
Contributor

TyHolc commented Aug 14, 2023

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
View this failed invocation of the CLA check for more information.
For the most up to date status, view the checks section at the bottom of the pull request.

@victorpasoshnikov Can you address this? I'm not sure why it still has an issue.

Checking in again. This one still has an issue with the CLA.

@victorpasoshnikov
Copy link
Collaborator

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
View this failed invocation of the CLA check for more information.
For the most up to date status, view the checks section at the bottom of the pull request.

@victorpasoshnikov Can you address this? I'm not sure why it still has an issue.

Checking in again. This one still has an issue with the CLA.

There was the same issue a few weeks ago.
Kaido Kert[email protected] #28Aug 1, 2023 08:59PM
Go to https://github.com/settings/emails on our profile and untick this box "Keep my email addresses private"
We are trying to resolve the CLA-bot not recognizing the anonymized addresses separately, but that's taking a while.
I've done what @kaidokert said and it looked helpful.
Now I see that contributor still is [email protected] instead of [email protected].
I've rechecked CLA then rescan but with the same negative result

@kaidokert kaidokert merged commit ac34795 into 24.lts.1+ Aug 21, 2023
324 of 325 checks passed
@kaidokert kaidokert deleted the 24.lts.1+-969 branch August 21, 2023 16:06
@kaidokert
Copy link
Member

I overrode the check here.

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.

4 participants