-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
HADOOP-18595. Fix "the the" and friends typos #5267
Conversation
@@ -122,7 +122,7 @@ Optimised for random IO, specifically the Hadoop `PositionedReadable` | |||
operations —though `seek(offset); read(byte_buffer)` also benefits. | |||
|
|||
Rather than ask for the whole file, the range of the HTTP request is | |||
set to that that of the length of data desired in the `read` operation | |||
set to the length of data desired in the `read` operation |
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.
This wording is better to my taste, please correct me if I'm wrong here
🎊 +1 overall
This message was automatically generated. |
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.
LGTM, thanks @neshkeev for the improvement.
I see you have touched quite a few files from past releases.
Let us wait for more members to review and sign off on this change.
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.
Can we change the release notes? they are part of the release voting? and it isn't going to help us any way here either
@ayushtkn , I didn't touch the names of the issues that are in the release notes, only the commentaries to the releases, so I believe no problems should arise here |
Those commentaries aren't written explicitly written, they are fetched from the jira itself, it is there in the release notes column of the Jira. To be precise, so that they can be extracted during the release and published, the same would have been published, and if old archived. |
@ayushtkn , I restored everything in the |
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.
Makes sense.
Changes LGTM
🎊 +1 overall
This message was automatically generated. |
Could this PR be merged, please? |
@neshkeev Could you pls resolve the conflicts? |
@dineshchitlangia , the conflicts have been resolved. It's weird that I haven't gotten the notification about the conflicts in the PR |
Signed-off-by: Nikita Eshkeev <neshkeev@yandex.ru>
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
@dineshchitlangia , could you please check if this PR can be merged and merge it if so? |
@dineshchitlangia , @ayushtkn , @slfan1989 , please could someone merge the PR? |
@neshkeev Thanks for your contribution! I will merge into trunk branch. @goiri @dineshchitlangia @ayushtkn Thank you very much! |
@neshkeev We need a jira, can you create one? I created JIRA: HADOOP-18595. Fix "the the" and friends typos, and modified the pr title. Thanks again for your contribution! @neshkeev |
This reverts commit 4de3112.
When reading the documentation I noticed a couple of "the the" typos, so I decided to fix them. IDK if I should request a JIRA ticket for it, but if so, please let me know and I'll amend the commit
Please notice that along with "the the" I also took liberty to fix a different typos like "and&" -> "and" and "can has" -> "has".
Also I'd like to inform you that I fixed a couple of "the the" typos in
RELEASENOTES*
files. I didn't touch the issues' names, since the linkRELEASENOTES File <-> JIRA
might be important. IDK if I should touch those files, so please advise.