]> git.lizzy.rs Git - rust.git/commit
projects / rust.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(merge: b9e3f3d 800c5f9)
Rollup merge of #87346 - rylev:rename-force-warn, r=nikomatsakis
authorEric Huss <eric@huss.org>
Wed, 21 Jul 2021 17:12:30 +0000 (10:12 -0700)
committerGitHub <noreply@github.com>
Wed, 21 Jul 2021 17:12:30 +0000 (10:12 -0700)
commit43e25751ff6f20941bef019bdb10bce32af8f178
treebb1f1d4339aa9d223e1c4053d8c773f00069bc07tree | snapshot
parentb9e3f3d5a21a24bf91e34a649896092dbad83a38commit | diff
parent800c5f9202ca5309bbe372bbb8f2d6f1c29e59a5commit | diff
Rollup merge of #87346 - rylev:rename-force-warn, r=nikomatsakis

Rename force-warns to force-warn

The renames the `--force-warns` option to `--force-warn`. This mirrors other lint options like `--warn` and `--deny` which are in the singular.

r? `@nikomatsakis`

cc `@ehuss` - this option is being used by Cargo. How do we make sure the transition to using the new name is as smooth as possible?
Empowering everyone to build reliable and efficient software.