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.
Use the latest config.guess and config.sub
Use SHA-256 for release signing
The last time I checked GPG - which was several years ago - GPG used SHA-1 as the default digest algorithm. I got into the habit of using
--digest-algo SHA256
to explicitly avoid SHA-1 in anticipation of Announcing the first SHA1 collision . (It was apparent the SHA-1 collision was coming based on Marc Stevens' work on hashclash).