sysinternals: Change the version pattern #3967
Merged
Conversation
This file contains 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
Ash258
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 current version pattern of sysinternals
Month.day.yeardoesn't allow most of the time to automatically upgrade.I propose to change to
year.Month.day. Since Month is still alphabetical name instead of a number it will still miss some update. However it will better than today, eg we can get the April 2020 update if we have the September 2019 version installed. Today it won't update since September > April in alphabetical order.Note: there is an numeric version of the date in the page where it's extracted, but looking on webarchive it doesn't evolve consistently with the "Update: .... " (however currently it's aligned)