On Wed, 24 Mar 2021 16:31:20 GMT, Claes Redestad <redes...@openjdk.org> wrote:
>> Aleksei Voitylov has updated the pull request incrementally with one >> additional commit since the last revision: >> >> fix style > > Looks good. The need to retain singleton/identity semantics of constants like > this when archiving in CDS has bitten us in the past. > Unknown command `backport` - for a list of valid commands use `/help`. There is the description on the SKARA/Backports page: https://wiki.openjdk.java.net/display/SKARA/Backports Backport Commit Command The /backport commit command can be used to quickly create a backport pull request for a given commit. Just navigate to the comment in source code hosting provider's web UI and add a comment consisting of "/backport <repo>". If the commit does not apply clean on the target repository then a message will be shown for the files with conflicts. The `The /backport commit command ` link points to: https://wiki.openjdk.java.net/display/SKARA/Commit+Commands#CommitCommands-/backport Commit Commands Syntax Description Applies the commit onto the given branch in the given repository and then shows to a link to create a pull request with the changes. The branch is optional and defaults to the master branch. If the commit does not apply then an message is shown describing the files containing conflicts. Examples What is the right way to create a backport to jdk16u? ------------- PR: https://git.openjdk.java.net/jdk/pull/3131
