Merged
Conversation
carlos-zamora
requested changes
Dec 5, 2022
Member
carlos-zamora
left a comment
carlos-zamora
left a comment
There was a problem hiding this comment.
Just the one question on _runtimeUseAcrylic
ghost
added
Needs-Author-Feedback
carlos-zamora
approved these changes
Dec 9, 2022
ghost
requested review from
DHowett
approved these changes
Dec 9, 2022
Member
DHowett
left a comment
DHowett
left a comment
There was a problem hiding this comment.
that_was_easy_button_xy7MRuvL.jpg
Can you project this up for servicing back to the right versions?
zadjii-msft
added
the
AutoMerge
|
Hello @zadjii-msft! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
DHowett
pushed a commit
that referenced
this pull request
Dec 12, 2022
This reverts #11372 and #11285, and brings #11180 to everyone, now that MSFT:37879806 has been serviced to everyone in [KB5011831](https://support.microsoft.com/en-gb/topic/april-25-2022-kb5011831-os-builds-19042-1682-19043-1682-and-19044-1682-preview-fe4ff411-d25a-4185-aabb-8bc66e9dbb6c)[1]. I tested this on my home Win10 laptop that's super old and doesn't have a functioning clock, but it does have that update at the very least. I don't think we had an issue tracking this? [1]: I'm pretty sure about this at least (cherry picked from commit a5c5b8a) Service-Card-Id: 87176746 Service-Version: 1.16
DHowett
pushed a commit
that referenced
this pull request
Dec 12, 2022
This reverts #11372 and #11285, and brings #11180 to everyone, now that MSFT:37879806 has been serviced to everyone in [KB5011831](https://support.microsoft.com/en-gb/topic/april-25-2022-kb5011831-os-builds-19042-1682-19043-1682-and-19044-1682-preview-fe4ff411-d25a-4185-aabb-8bc66e9dbb6c)[1]. I tested this on my home Win10 laptop that's super old and doesn't have a functioning clock, but it does have that update at the very least. I don't think we had an issue tracking this? [1]: I'm pretty sure about this at least (cherry picked from commit a5c5b8a) Service-Card-Id: 87176745 Service-Version: 1.15
|
🎉 Handy links: |
|
🎉 Handy links: |
This pull request was closed.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This reverts #11372 and #11285, and brings #11180 to everyone, now that MSFT:37879806 has been serviced to everyone in KB5011831[1].
I tested this on my home Win10 laptop that's super old and doesn't have a functioning clock, but it does have that update at the very least.
I don't think we had an issue tracking this?
[1]: I'm pretty sure about this at least