-
Notifications
You must be signed in to change notification settings - Fork 174
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
7420: Update Japanese translation for rules #308
Conversation
Signed-off-by: Motohiro Ohno <m-ohno@atware.co.jp>
Hi @mohno007, welcome to this OpenJDK project and thanks for contributing! We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user mohno007" as summary for the issue. If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing |
.../resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties
Outdated
Show resolved
Hide resolved
fac9758
to
48d36d4
Compare
Thanks @mohno007! Let me know if you need any help with verifying the OCA status! Meanwhile, I've asked a friend in Japan to verify the texts. |
I run into a problem with OCA. I have already contacted Oracle Support by email and currently waiting for a response.
Thank you. |
@edvbld - can you help? What's the best way to help @mohno007 proceed with his application? |
Hi @davidbuckjp! Any chance you could take a look at this? |
Have you heard back from Oracle Support yet? |
Hi, please send me an e-Mail at dalibor.topic@oracle.com and I can try to assist you to find a resolution for the OCA issue. |
/signed |
Thank you! Please allow for up to two weeks to process your OCA, although it is usually done within one to two business days. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated! |
Webrevs
|
/reviewers 2 |
@thegreystone |
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.
Needs an updated copyright year.
.../resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties
Outdated
Show resolved
Hide resolved
As you may know, I can sign the OCA. |
@mohno007 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 57 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 (@thegreystone, @aptmac) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Hi @mohno007! This PR is ready for integration! Please type /integrate in a new comment. |
Also - @mohno007, are you in the JMC dev slack? If not, would you like to be? Please ping me, and I'd be happy to invite you. |
Hi @mohno007 - a friendly reminder that this PR is ready for integration! Please write /integrate in a new comment in this PR to integrate. |
/integrate Thank you for reviewing and reminding me. |
/sponsor |
Going to push as commit 0002999.
Your commit was automatically rebased without conflicts. |
@thegreystone @mohno007 Pushed as commit 0002999. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This PR updates/improves Japanese translation of rules and its descriptions.
Update
messages.properties
made after the last update date of themessages_ja.properties
.Rule 2.0
.You can see decoded version of
messages_ja
using this script:Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jmc pull/308/head:pull/308
$ git checkout pull/308
Update a local copy of the PR:
$ git checkout pull/308
$ git pull https://git.openjdk.java.net/jmc pull/308/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 308
View PR using the GUI difftool:
$ git pr show -t 308
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jmc/pull/308.diff