-
Notifications
You must be signed in to change notification settings - Fork 178
8273278: Support XSLT on GraalVM Native Image--deterministic bytecode generation in XSLT #73
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
8273278: Support XSLT on GraalVM Native Image--deterministic bytecode generation in XSLT #73
Conversation
… generation in XSLT
👋 Welcome back jovanstevanovic! A progress list of the required criteria for merging this PR into |
Same here, please change PR title to "Backport f690a01f1e5de4ace39aefad656cb7c99f9ec4e1" to have the bots recognize the backport correctly. |
This backport pull request has now been updated with issue from the original commit. |
|
@jovanstevanovic This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. 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 50 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. ➡️ To flag this PR as ready for integration with the above commit message, type |
Done. |
OK, great. So for this one, you'll only need to add the jdk17u-fix-request label to the JBS bug and write a comment why you want to backport, what's the risk and what testing you did. Then wait for approval. After you have approval, you can integrate it. No need for PR review necessary since the backport applied clean. |
Done. JBS issue is updated. |
@jovanstevanovic This one was approved. You can integrate it... |
/integrate |
@jovanstevanovic |
/sponsor |
Going to push as commit 20afdfd.
Your commit was automatically rebased without conflicts. |
@RealCLanger @jovanstevanovic Pushed as commit 20afdfd. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This PR is backporting changes from PR on the OpenJDK repo.
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk17u pull/73/head:pull/73
$ git checkout pull/73
Update a local copy of the PR:
$ git checkout pull/73
$ git pull https://git.openjdk.java.net/jdk17u pull/73/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 73
View PR using the GUI difftool:
$ git pr show -t 73
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk17u/pull/73.diff