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

Version subcommand should handle verbose flag #3613

Closed
matklad opened this issue Jan 30, 2017 · 3 comments
Closed

Version subcommand should handle verbose flag #3613

matklad opened this issue Jan 30, 2017 · 3 comments
Labels
C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` Command-version

Comments

@matklad
Copy link
Member

matklad commented Jan 30, 2017

There is cargo --version and cargo version. #3584 was implemented only for the first one. I wonder if we should just special case the version subcommand to avoid duplication and similar issues in the future?

@matklad
Copy link
Member Author

matklad commented Jan 30, 2017

Or maybe to deprecate it altogether? why do we need to ways to print a version anyway?

@alexcrichton
Copy link
Member

I'd prefer to keep it around, but special casing to remove duplication sounds find to me!

@carols10cents carols10cents added C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` Command-version labels Sep 29, 2017
@matklad matklad mentioned this issue Mar 12, 2018
@ehuss
Copy link
Contributor

ehuss commented Nov 9, 2018

This was fixed in #6076.

@ehuss ehuss closed this as completed Nov 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` Command-version
Projects
None yet
Development

No branches or pull requests

4 participants