chore: restore the verbatim Unlicense text - #54
Merged
Conversation
The closing line had drifted into three variants across the repositories: `http://unlicense.org/` without a trailing newline, `https://unlicense.org` without the trailing slash, and a mix of the two. The file now matches https://unlicense.org/UNLICENSE byte for byte.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 closing line of the Unlicense text had drifted into three variants across the repositories:
http://unlicense.org/with no trailing newlinehttps://unlicense.orgwithout the trailing slashLICENSEis tier 1, byte-identical everywhere. The file now matches https://unlicense.org/UNLICENSE exactly. Nothing but that one line changes;firewallfabrikis untouched because it is GPL.