Repository navigation
[stable35] chore(stable35): align 3rdparty submodule with stable35 - #8538
Merged
Merged
Conversation
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
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.
Summary
Update the
3rdpartysubmodule pointer onstable35from9b2d970toa31aa2a, the current HEAD ofLibreSign/3rdparty:stable35after merging LibreSign/3rdparty#103.This restores the expected invariant that
LibreSign/libresign:stable35points to the HEAD of the correspondingLibreSign/3rdparty:stable35branch.Context
The previous LibreSign stable35 backports had referenced commits from the
3rdpartymain line directly. LibreSign/3rdparty#103 incorporated the required dependency history into3rdparty:stable35. Its merge produceda31aa2ace5dedbd5e722e6a367a6bfffb0b97ce6, which is now the correct stable35 submodule target.Change
Only the
3rdpartygitlink changes:9b2d970391b802245dc2bcf8ee384ccf44d70bf3a31aa2ace5dedbd5e722e6a367a6bfffb0b97ce6No application code changes are included.