Skip to content
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

Minor grammar error in cargo --help output #13601

Closed
mrobinson opened this issue Mar 18, 2024 · 0 comments · Fixed by #13602
Closed

Minor grammar error in cargo --help output #13601

mrobinson opened this issue Mar 18, 2024 · 0 comments · Fixed by #13602
Labels
C-bug Category: bug S-triage Status: This issue is waiting on initial triage.

Comments

@mrobinson
Copy link
Contributor

Problem

There is a minor grammar error in the cargo --help output. This is a tiny thing, so apologies if this is too much of a nit, but:

      --frozen              Require Cargo.lock and cache are up to date
      --locked              Require Cargo.lock is up to date

Typically "require" is followed by the infinitive. The current wording makes the sentence a little bit harder to read. Normally, this would be something like "Require Cargo.lock and cache to be up to date."

Steps

No response

Possible Solution(s)

No response

Notes

No response

Version

cargo 1.76.0 (c84b36747 2024-01-18)
release: 1.76.0
commit-hash: c84b367471a2db61d2c2c6aab605b14130b8a31b
commit-date: 2024-01-18
host: x86_64-unknown-linux-gnu
libgit2: 1.7.1 (sys:0.18.1 vendored)
libcurl: 8.5.0-DEV (sys:0.4.70+curl-8.5.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: Ubuntu 23.10 (mantic) [64-bit]
@mrobinson mrobinson added C-bug Category: bug S-triage Status: This issue is waiting on initial triage. labels Mar 18, 2024
@bors bors closed this as completed in 3e7852b Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: bug S-triage Status: This issue is waiting on initial triage.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant