Closed
Conversation
SpidFightFR
force-pushed
the
update-mesa
branch
from
aa1cd83 to
10c81e3
Compare
Contributor
Author
|
I'm aware there's two commits, that's because i'm not sure mesa 23.3.0 will work properly, i keep the second one as a fallback just in case. |
Member
|
can we go back to waiting until the |
Contributor
Author
Sorry i completely forgot... yes, for sure! |
SpidFightFR
force-pushed
the
update-mesa
branch
from
10c81e3 to
d99138f
Compare
Contributor
Author
|
damn... one moment. |
Contributor
Author
|
Oh i didn't realize someone already pushed mesa 23.2.7, i was wondering what happened... |
Contributor
|
Bro, hurry up |
Member
|
bro, chill |
Contributor
Author
Yo. |
Contributor
Author
|
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.
Testing the changes
Local build testing