fix-typos

[sheshnath-at-knoldus]

fixes some typos in lintcheck

changelog: None

[rustbot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Jarcho (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[Jarcho]

LintcheckConfig is named that way on purpose to match the tool name. The other changes are fine.

[sheshnath-at-knoldus]

ok @Jarcho

[sheshnath-at-knoldus]

Do you think I should revert the changes for LintcheckConfig?

[Jarcho]

Yes. Reverting just the second commit would be great.

[Jarcho]

Just need to have the commits squashed and then we're good.

[sheshnath-at-knoldus]

@Jarcho who will squashed the commits ?

[Jarcho]

You will have to.

[rustbot]

There are merge commits (commits with multiple parents) in your changes. We have a no merge policy so these commits will need to be removed for this pull request to be merged.

You can start a rebase with the following commands:

$ # rebase
$ git pull --rebase https://github.com/rust-lang/rust-clippy.git master
$ git push --force-with-lease

The following commits are merge commits:

• 2043d9f

[Jarcho]

I would generally use git rebase -i HEAD~N to squash the last N commits together. There are other more concise ways to do it, but they're also more open to typos leading to problems.

[sheshnath-at-knoldus]

so what should i do next ?

[Jarcho]

Assuming your local state and github's are the same the easiest way would be git reset HEAD~3 (will undo the last three commits), then discard the changes and force push.

Note that git reset is useful here since you only want the first commit. If you wanted to keep all of them then it wouldn't work.

[sheshnath-at-knoldus]

thanks it worked

[Jarcho]

Thank you. @bors r+

[bors]

📌 Commit b9716dd has been approved by Jarcho

It is now in the queue for this repository.

[bors]

⌛ Testing commit b9716dd with merge 377d72a...

[bors]

☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test
Approved by: Jarcho
Pushing 377d72a to master...