Merged
Conversation
Contributor
Author
|
There are two commits in the PR which could in principle be squashed. I kept them both as a reminder, because it's important to update to the current upstream (i.e. flathub) code base before running Updating to the upstream state in an intermediate step does not hurt, because |
Contributor
Author
|
Merged flathub/org.audiveris.audiveris#9, and updated |
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
2 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.
@hbitteur:
This PR updates the flatpak/flathub submodule to 5.8.0.
Here is the Flatpak PR for beta branch.
I will wait until this shows up in flathub beta (probably tomorrow) and give it a quick test.
If that succeeds, I will create a PR for the flathub master branch.
That might add another empty merge commit in flatpak/flathub.