-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8257620: Do not use objc_msgSend_stret to get macOS version #153
Conversation
👋 Welcome back btaylor! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issue from the original commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clean except for referenced context changes. Lgtm.
@benty-amzn This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 41 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@phohensee) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Patched file location difference: It seems it's not possible to apply this patch avoiding manual merge in a way described, right? |
You are right. From my reading, @benty-amzn just reverted what you did(step-1) and re-applied it(step-3) after JDK-8257620. There's a typo in his description. It should be 'JDK-8269850' rather than 'JDK-826985' in step-3. |
Xin is right, edited the PR to use the correct bug id. |
I meant not that but the following:
It seems it's impossible to apply this patch following the way in this description. |
I think the reason your backport was unclean is related to these 2 lines:
I believe if you follow the instructions in the warning and raise the rename limit, inexact rename detection will find the correct file and no manual resolution will be required - that's what happened for me, at least. |
@benty-amzn Thanks for this tip! |
/integrate |
@benty-amzn |
/sponsor |
Going to push as commit 2abc206.
Your commit was automatically rebased without conflicts. |
@phohensee @benty-amzn Pushed as commit 2abc206. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This backports JDK-8257620 for parity with Oracle JDK8 and OpenJDK 11+.
The backport is not clean because JDK-8269850 was applied first in 8u. If that change is backed out and reapplied after this backport, both are clean.
Change applied with:
git revert 43cfe27fa3a11dd6d4fffcb1c1336ac7fdd0233b
(backout JDK-8269850)git backport --from https://github.com/openjdk/jdk d4c7db5060978302382549246f9ad6831f19377d
(apply JDK-8257620)git backport --from https://github.com/openjdk/jdk 3b1b8fc646493eae5f4df828afe29abb75fa5e60
(re-apply JDK-8269850)git rebase -i HEAD~3
(squash commits)Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev pull/153/head:pull/153
$ git checkout pull/153
Update a local copy of the PR:
$ git checkout pull/153
$ git pull https://git.openjdk.org/jdk8u-dev pull/153/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 153
View PR using the GUI difftool:
$ git pr show -t 153
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/153.diff