Update mangohud version #109
Open
+0
−579
Conversation
This file contains 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
|
The patch doesn't apply cleanly on 0.7.2, I'll look into that. |
|
I noticed |
|
Our patch was upstreamed (see: flightlessmango/MangoHud#1262 ) so we can just remove the patch but at this point, is it necessary to keep mangohud in this repo? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
On Nobara 41, our mangohud fork is masked by mangohud 0.7.2 packages. I'm not 100% sure just bumping the version number in the spec file is enough so let me know if anything else is needed.
Also, should we consider sending our patch for increased logging upstream? That would free us from maintaining a fork