diff options
| author | bors <bors@rust-lang.org> | 2024-03-12 10:00:15 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-03-12 10:00:15 +0000 |
| commit | 3a149111ba2ad470c43d58cc1879f85209112b8e (patch) | |
| tree | da454ec9e571a5d9d436a4aeccdbbde27dc50432 /compiler/rustc_codegen_gcc | |
| parent | a8a737172801f7f6afb74659fae95004b5da6f53 (diff) | |
| parent | f472b5071058360c99ee18ee79b2142fe8f215cc (diff) | |
| download | rust-3a149111ba2ad470c43d58cc1879f85209112b8e.tar.gz rust-3a149111ba2ad470c43d58cc1879f85209112b8e.zip | |
Auto merge of #12469 - pavedroad:master, r=y21
chore: fix some typos Thank you for making Clippy better! We're collecting our changelog from pull request descriptions. If your PR only includes internal changes, you can just write `changelog: none`. Otherwise, please write a short comment explaining your change. It's also helpful for us that the lint name is put within backticks (`` ` ` ``), and then encapsulated by square brackets (`[]`), for example: ``` changelog: [`lint_name`]: your change ``` If your PR fixes an issue, you can add `fixes #issue_number` into this PR description. This way the issue will be automatically closed when your PR is merged. If you added a new lint, here's a checklist for things that will be checked during review or continuous integration. - \[x] Followed [lint naming conventions][lint_naming] - \[ ] Added passing UI tests (including committed `.stderr` file) - \[ ] `cargo test` passes locally - \[ ] Executed `cargo dev update_lints` - \[ ] Added lint documentation - \[x] Run `cargo dev fmt` [lint_naming]: https://rust-lang.github.io/rfcs/0344-conventions-galore.html#lints Note that you can skip the above if you are just opening a WIP PR in order to get feedback. Delete this line and everything above before opening your PR. --- *Please write a short comment explaining your change (or "none" for internal only changes)* changelog:
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions
