Skip to content
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

8299563: Fix typos #10029

Closed
wants to merge 9 commits into from
Closed

8299563: Fix typos #10029

wants to merge 9 commits into from

Conversation

mernst
Copy link
Contributor

@mernst mernst commented Aug 25, 2022


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 10029

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10029.diff

@bridgekeeper bridgekeeper bot added the oca Needs verification of OCA signatory status label Aug 25, 2022
@bridgekeeper
Copy link

bridgekeeper bot commented Aug 25, 2022

Hi @mernst, 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 /signed in a comment in this pull request.

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 mernst" 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 /covered in a comment in this pull request.

@openjdk
Copy link

openjdk bot commented Aug 25, 2022

@mernst The following labels will be automatically applied to this pull request:

  • client
  • compiler
  • core-libs
  • hotspot
  • i18n
  • javadoc
  • jmx
  • net
  • nio
  • security
  • serviceability

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added serviceability serviceability-dev@openjdk.org hotspot hotspot-dev@openjdk.org i18n i18n-dev@openjdk.org javadoc javadoc-dev@openjdk.org security security-dev@openjdk.org jmx jmx-dev@openjdk.org nio nio-dev@openjdk.org client client-libs-dev@openjdk.org core-libs core-libs-dev@openjdk.org compiler compiler-dev@openjdk.org net net-dev@openjdk.org labels Aug 25, 2022
@mernst
Copy link
Contributor Author

mernst commented Aug 25, 2022

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 mernst" as summary for the issue.

Done: https://bugs.openjdk.org/browse/SKARA-1566

@bridgekeeper bridgekeeper bot removed the oca Needs verification of OCA signatory status label Aug 25, 2022
@@ -753,7 +753,7 @@ ZEXTERN int ZEXPORT deflateParams OF((z_streamp strm,
Then no more input data should be provided before the deflateParams() call.
If this is done, the old level and strategy will be applied to the data
compressed before deflateParams(), and the new level and strategy will be
applied to the the data compressed after deflateParams().
applied to the data compressed after deflateParams().
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an issue for the upstream zlib project, we probably don't want to change it here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree. See madler/zlib@5752b17 which is in the zlib development branch and addresses a wide range of typos.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. I backed out the change to zlib.

@jaikiran
Copy link
Member

jaikiran commented Sep 5, 2022

Hello Michael @mernst, these changes are mostly fine. However, they are spread across files which reside in different areas of the JDK. For changes like these, we usually split up the changes into different PRs to help reviewers of specific areas focus on the individual PRs.

Would you be willing to split this PR into separate ones. I would recommend starting with one PR which includes changes that are part of test/jdk/java, test/jdk/jdk and test/jdk/jni. If you can come up with that PR, then I'll go ahead and create a JBS issue for it and you can then link the PR against that issue.

@mernst
Copy link
Contributor Author

mernst commented Sep 5, 2022

these changes are mostly fine.

Can you be specific about the exact problems that you noticed that prevented you from saying "these changes are fine"? It doesn't seem useful to make a pull request with known deficiencies.

we usually split up the changes into different PRs to help reviewers of specific areas focus on the individual PRs.

Feel free to split up the pull request, if you feel that specific expertise in specific parts of the JDK is necessary to review these changes.

@@ -1050,7 +1050,7 @@ public int indexOf(int elem)
* you call getCurrentPos() and the return is 0, the next
* fetch will take place at index 1.
*
* @return The the current position index.
* @return The current position index.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that there is an inconsistent change here, albeit insignificant. In NodeSet, the capital 'The' is removed after the @return, while the lowercase 'the' is removed here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for pointing out the inconsistency. I have fixed it. (I noticed many violations of the official Javadoc style, but this is not the right pull request to fix them.)

@SWinxy
Copy link
Contributor

SWinxy commented Sep 23, 2022

Can you be specific about the exact problems that you noticed that prevented you from saying "these changes are fine"?

These changes are fine. I don't see an instance where the duplicated words would mean a change in the specification.

@jaikiran
Copy link
Member

Hello Michael,

these changes are mostly fine.

Can you be specific about the exact problems that you noticed that prevented you from saying "these changes are fine"? It doesn't seem useful to make a pull request with known deficiencies.

I wasn't implying this PR had deficiencies. What I meant was, to be able to have this reviewed, in addition to code changes this will also need a issue to be created and linked to this PR (and the PR title changed to the form <bugid>: <bug summary>).
I have now created https://bugs.openjdk.org/browse/JDK-8294321. Splitting these changes into smaller PRs instead of one big one that touches several different areas of the JDK and 108 files, will help reviewers.

@mernst
Copy link
Contributor Author

mernst commented Sep 24, 2022

Splitting these changes into smaller PRs instead of one big one that touches several different areas of the JDK and 108 files, will help reviewers.

OK. I'll repeat my comment from before:

Feel free to split up the pull request, if you feel that specific expertise in specific parts of the JDK is necessary to review these changes.

@openjdk
Copy link

openjdk bot commented Sep 25, 2022

@mernst this pull request can not be integrated into master due to one or more merge conflicts. To resolve these merge conflicts and update this pull request you can run the following commands in the local repository for your personal fork:

git checkout typos-typos
git fetch https://git.openjdk.org/jdk master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push

@openjdk openjdk bot added the merge-conflict Pull request has merge conflict with target branch label Sep 25, 2022
@openjdk openjdk bot removed the merge-conflict Pull request has merge conflict with target branch label Sep 25, 2022
@openjdk
Copy link

openjdk bot commented Dec 27, 2022

@AlanBateman
The net label was successfully removed.

@openjdk openjdk bot removed the nio nio-dev@openjdk.org label Dec 27, 2022
@openjdk
Copy link

openjdk bot commented Dec 27, 2022

@AlanBateman
The nio label was successfully removed.

@openjdk openjdk bot removed the security security-dev@openjdk.org label Dec 27, 2022
@openjdk
Copy link

openjdk bot commented Dec 27, 2022

@AlanBateman
The security label was successfully removed.

@openjdk
Copy link

openjdk bot commented Jan 3, 2023

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

8299563: Fix typos

Reviewed-by: lancea, aivanov, sspitsyn

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

  • 44be5ed: 8219810: javac throws NullPointerException
  • b9758d2: 8200610: Compiling fails with java.nio.file.ReadOnlyFileSystemException

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.

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 (@LanceAndersen, @aivanov-jdk, @sspitsyn) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jan 3, 2023
@sspitsyn
Copy link
Contributor

sspitsyn commented Jan 3, 2023

Michael, I've reviewed the changes but the JDK-8294321 seems to be already resolved. So, what JBS issue are you actually trying to fix?

@plummercj
Copy link
Contributor

Michael, I've reviewed the changes but the JDK-8294321 seems to be already resolved. So, what JBS issue are you actually trying to fix?

It's closed because #11385 used it to fix some of the typos. #11385 should have used a new issue, but now instead a new issue is needed for the remaining typos.

@jaikiran
Copy link
Member

jaikiran commented Jan 4, 2023

Hello Michael, I've created https://bugs.openjdk.org/browse/JDK-8299563 to track this final few typos. Could you please update the title of this PR to 8299563: Fix typos? That should then allow you to proceed using this PR. Please also merge with latest master branch once more since some typo fixes from this PR have been merged recently. Thank you for your patience.

@mernst mernst changed the title 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni 8299563: Fix typos Jan 4, 2023
@mernst
Copy link
Contributor Author

mernst commented Jan 4, 2023

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Jan 4, 2023
@openjdk
Copy link

openjdk bot commented Jan 4, 2023

@mernst
Your change (at version 6147b06) is now ready to be sponsored by a Committer.

@aivanov-jdk
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Jan 4, 2023

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

  • 44be5ed: 8219810: javac throws NullPointerException
  • b9758d2: 8200610: Compiling fails with java.nio.file.ReadOnlyFileSystemException

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jan 4, 2023
@openjdk openjdk bot closed this Jan 4, 2023
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Jan 4, 2023
@openjdk
Copy link

openjdk bot commented Jan 4, 2023

@aivanov-jdk @mernst Pushed as commit 7dcc689.

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

@mernst mernst deleted the typos-typos branch January 4, 2023 22:34
@mernst
Copy link
Contributor Author

mernst commented Jan 4, 2023

Thank you @jaikiran @LanceAndersen @aivanov-jdk !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core-libs core-libs-dev@openjdk.org integrated Pull request has been integrated serviceability serviceability-dev@openjdk.org
Development

Successfully merging this pull request may close these issues.

10 participants