-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Subcommand wasn't recognized #73
Comments
While I intellectually understand why one'd report the fourth duplicate of #68 I will never really understand the necessity for such axion. |
Well if you left #68 open until the issue was fixed (even if not a bug in cargo-update itself) people would see it and stop opening new issues (at least I wouldn't have). |
Well if people did their due diligence and went through closed issues they'd see the previous four issues on the topic :v oh well |
This has finally made it into the latest nightly |
Thank @kbknapp, eternal praise be unto him. |
When I run
cargo install-update -a
I get:The text was updated successfully, but these errors were encountered: