Bump vendored optparse to latest master #5466
Merged
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
simi
approved these changes
Apr 11, 2022
deivid-rodriguez
pushed a commit
that referenced
this pull request
Apr 20, 2022
Bump vendored optparse to latest master (cherry picked from commit 8430d0d)
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.
What was the end-user or developer problem that led to this PR?
I made a PR a while ago to optparse to use relative requires when possible: ruby/optparse#28. But I never backported it here even if it was my main motivation (to have our requires fully consistent).
What is your fix for the problem, implemented in this PR?
Get in sync with the latest changes in the upstream library.
Make sure the following tasks are checked