Pull code from urlesc repo #35
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
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
|
@mna Does this look fine from a licensing standpoint? |
|
IANAL but that's the same license as Go so that should be good! Also, you should add yourself along with me (and maybe add "& Contributors", I usually do this for eventual PRs from the community, though again, not a lawyer :D ). |
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
|
Thanks!
Makes sense, applied. |
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.
Pulled code from the urlesc repo because the repo has been archived. I can remove
QueryEscapebut just replacingurlesc.Escapewithurl.Stringchanges the current behavior, so using urlesc for now.Signed-off-by: Yuki Okushi jtitor@2k36.org