Unnecessary change --update_cache to --update #91
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zlatanvasovic
suggested changes
Apr 23, 2020
Author
|
After a closer look, the ArgParse library considers that passing --update as an argument is the same as passing --update_cache. So I close this pull request, which is no longer necessary. |
clesecq
changed the title
Contributor
|
@StelFux Thanks for the work on this nevertheless. 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The majority of clients that allow to update their cache use --update, this allows to keep a certain unity. One of the consequences encountered with topgrade (utility trying to update the program maximum), not knowing which clients are facing it, it tries the most common method.