Add license at the top of files #478
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
lantiga
force-pushed
the
license-in-files
branch
from
532510f
to
da71ade
Compare
awaelchli
approved these changes
Jan 5, 2024
|
Ubuntu is failing on the torch.compile test, does this ring any bell? |
Borda
approved these changes
Jul 14, 2024
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.
lit-llama is being used in other projects, often vendored (individual files taken out and reused).
This is not a bad thing per se, but we need to make sure the license and authorship are clear when this happens.
This PR adds licenses at the top of every file, just like we do for PyTorch Lightning and Fabric.