-
Notifications
You must be signed in to change notification settings - Fork 388
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
CLDR-18323 v47: Pourover of MessageFormat 2.0 #4385
CLDR-18323 v47: Pourover of MessageFormat 2.0 #4385
Conversation
939ef84
to
509f907
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
I can merge if you are unable to, Addison. |
@macchiati I don't have permission. I left the "completes the ticket" unchecked. Does that mean I can reuse the ticket for the eventual set of correx? |
091d267
to
19ecf67
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
I just merged.
Yes, please reuse the ticket for that. |
But nuke the branch; it gets very mixed up if you continue to use it. |
CLDR-18323
This PR contains the pourover of MessageFormat 2.0 for the LDML47 release. Note that there are a few pending changes. This is for consideration by CLDR-TC.
ALLOW_MANY_COMMITS=true