mirror of
https://github.com/rust-lang/cargo.git
synced 2025-09-25 11:14:46 +00:00

This fixes an issue where `--quiet` doesn't work with commands that have subcommands. This is because `config_configure` only looks at the global and top-level subcommand, and not deeper subcommands. The issue was that `--quiet` was not defined as a global flag. This was changed in https://github.com/rust-lang/cargo/pull/6358 in order to give a better help message for `cargo test --quiet`. I don't remember if clap just didn't support overriding at the time, or if we just didn't know how it worked. Anyways, it seems to work to override it now, so I think it should be fine to mark it as global. This should bring in `--quiet` more in-line with how `--verbose` works. This means that `--quiet` is now accepted with `cargo report`, `cargo help`, and `cargo config`. This also fixes `--quiet` with `cargo clean gc`. This should also help with supporting `--quiet` with the new `cargo owner` subcommands being added in https://github.com/rust-lang/cargo/pull/11879. Fixes #12957
20 lines
821 B
Plaintext
20 lines
821 B
Plaintext
Check correctness of crate manifest
|
|
|
|
Usage: cargo[EXE] verify-project [OPTIONS]
|
|
|
|
Options:
|
|
-v, --verbose... Use verbose output (-vv very verbose/build.rs output)
|
|
-q, --quiet Do not print cargo log messages
|
|
--color <WHEN> Coloring: auto, always, never
|
|
--config <KEY=VALUE> Override a configuration value
|
|
-Z <FLAG> Unstable (nightly-only) flags to Cargo, see 'cargo -Z help' for details
|
|
-h, --help Print help
|
|
|
|
Manifest Options:
|
|
--manifest-path <PATH> Path to Cargo.toml
|
|
--frozen Require Cargo.lock and cache are up to date
|
|
--locked Require Cargo.lock is up to date
|
|
--offline Run without accessing the network
|
|
|
|
Run `cargo help verify-project` for more detailed information.
|