Update license locations #29
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
|
Hi @hseg thanks for your contribution, and sorry I need time to review the other one a bit latter. |
|
On Wed, Feb 21, 2024 at 06:26:46AM -0800, 尹良灿 wrote:
Hi @hseg thanks for your contribution, and sorry I need time to review the other one a bit latter.
No worries -- it is a larger patch with more implications, after all
|
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.
Since RFC16, known license locations have been shuffled a bit.
This also adds (commented-out) a function to get the common licenses (which don't need to be installed per-project), in case we later want to either skip such licenses, or warn if no license file could be found for an uncommon license