Restore original authorship of the arm64 release support work - #27
Merged
maoueh merged 7 commits intoAug 12, 2026
Merged
Conversation
…support PR #26 re-implemented the arm64 multi-arch release work of PR #25 from scratch, so the six original commits by Arthur Kepler (@excalq) never landed here and their authorship was lost. This merge brings that history back into the branch. It is an "ours" merge: the tree is byte-identical to the pre-merge state, so nothing in the working tree changes. Only the commit graph gains the original commits, restoring authorship and GitHub contribution credit for the work that PR #26 shipped. Original PR: #25 Superseding PR: #26
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.
What
Merges the history of #25 into
release/v3.x-fhso that the six original commits by @excalq become part of this branch.This PR changes no files. It is an "ours" merge: the resulting tree is byte-identical to
release/v3.x-fhas it stands today. GitHub will show "0 files changed", which is expected.Why
#26 re-implemented the arm64 multi-arch release work of #25 from scratch. The shipped result is functionally the work proposed in #25, but because none of the original commits landed, @excalq lost all authorship and contribution credit for it. This merge brings those commits into the branch history so the credit is restored, without touching a single line of the current tree.
Important
This must be merged with "Create a merge commit". Squash or rebase merging would flatten the ancestry and defeat the entire purpose of the PR.