8327631: Update IANA Language Subtag Registry to Version 2024-03-07

[GoeLin]

One of the required updates of meta information.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8327631 needs maintainer approval

Issue

• JDK-8327631: Update IANA Language Subtag Registry to Version 2024-03-07 (Enhancement - P4 - Approved)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk22u.git pull/136/head:pull/136
$ git checkout pull/136

Update a local copy of the PR:
$ git checkout pull/136
$ git pull https://git.openjdk.org/jdk22u.git pull/136/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 136

View PR using the GUI difftool:
$ git pr show -t 136

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk22u/pull/136.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back goetz! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@GoeLin 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:

8327631: Update IANA Language Subtag Registry to Version 2024-03-07

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 7 new commits pushed to the master branch:

• 3d99b8f: 8309218: java/util/concurrent/locks/Lock/OOMEInAQS.java still times out with ZGC, Generational ZGC, and SerialGC
• 64b4949: 8328316: Finisher cannot emit if stream is sequential and integrator returned false
• bcf0d25: 8329823: RISC-V: Need to sync CPU features with related JVM flags
• dbaca7a: 8325028: (ch) Pipe channels should lazily set socket to non-blocking mode on first use by virtual thread
• 3b35164: 8329545: [s390x] Fix garbage value being passed in Argument Register
• 817cf13: 8328702: C2: Crash during parsing because sub type check is not folded
• 98a63a8: 8328589: unify os::breakpoint among posix platforms

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

⚠️ @GoeLin This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[mlbridge]

Webrevs

• 00: Full (afa1eda1)

[GoeLin]

/integrate

[openjdk]

Going to push as commit c45dbbc.
Since your change was applied there have been 8 commits pushed to the master branch:

• 11adb6e: 8329656: assertion failed in MAP_ARCHIVE_MMAP_FAILURE path: Invalid immediate -5 0
• 3d99b8f: 8309218: java/util/concurrent/locks/Lock/OOMEInAQS.java still times out with ZGC, Generational ZGC, and SerialGC
• 64b4949: 8328316: Finisher cannot emit if stream is sequential and integrator returned false
• bcf0d25: 8329823: RISC-V: Need to sync CPU features with related JVM flags
• dbaca7a: 8325028: (ch) Pipe channels should lazily set socket to non-blocking mode on first use by virtual thread
• 3b35164: 8329545: [s390x] Fix garbage value being passed in Argument Register
• 817cf13: 8328702: C2: Crash during parsing because sub type check is not folded
• 98a63a8: 8328589: unify os::breakpoint among posix platforms

Your commit was automatically rebased without conflicts.

[openjdk]

@GoeLin Pushed as commit c45dbbc.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.