-
Notifications
You must be signed in to change notification settings - Fork 12.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
remove repetitive words #113717
remove repetitive words #113717
Conversation
r? @eholk (rustbot has picked a reviewer for you, use r? to override) |
The Miri subtree was changed cc @rust-lang/miri Portable SIMD is developed in its own repository. If possible, consider making this change to rust-lang/portable-simd instead. |
This comment has been minimized.
This comment has been minimized.
r? @Nilstrieb Please include some description of what you did and why you did it in your main post. |
Your git history seems to include some other branch. You'll have to rebase on a current master to get rid of those. |
Those commits accidentally got into master due to a bot glitch and then were removed but they're still in your branch. try
and then drop ( Alternatively hard-reset your branch onto the current upstream master and then cherry-pick just your commit from your remote and then force-push that (careful with that approach, doing it in the wrong order will erase your commit entirely). |
Thanks! |
Looks like they're still there. I'll clean up the history for you. |
9586c9f
to
4d6e426
Compare
or not... |
Sorry, I seem to have done something wrong with the remote branch, causing it to close.. |
I will resubmit and reopen later. Please wait me a few minutes |
Done |
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.
Most of the time "the the" or "is is" are typos.
But I think "that that" is more ambiguous. It can be a a mistake. But it can also be valid. On the other hand some uses of "that" are optional. So it's more a style question whether the optional ones should be removed, be kept to reduce churn or be rephrased to something less confusing.
I don't know what the policy here is.
Do I need to roll back the changes related to |
friendly ping~ |
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.
Almost all the that that
seem correct, so can you drop them? The one in libtest is pretty weird and I've suggested better wording.
Signed-off-by: cui fliter <imcusg@gmail.com>
Modified, please review again. |
@bors r+ rollup |
remove repetitive words
remove repetitive words
…iaskrgr Rollup of 8 pull requests Successful merges: - rust-lang#112858 (Update Android system definitions and add riscv-linux-android as tier 3 target) - rust-lang#113717 (remove repetitive words) - rust-lang#113725 (Move MinGW linker dist option to proper section) - rust-lang#113740 (Update `.gitmodules` to use shallow submodule clones) - rust-lang#113889 (Fix ice tests when librustc-driver is linked dynamically) - rust-lang#113906 (etc: add `RUSTC_BOOTSTRAP` to rust-analyzer config) - rust-lang#113920 (fix(resolve): report unresolved imports firstly) - rust-lang#114111 (Improve test case for experimental API remove_matches) r? `@ghost` `@rustbot` modify labels: rollup
No description provided.