-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add licensing information #2
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all seems really good overall, thanks again for all the effort analyzing all that upstream history!
I'm only noting down some tiny details (i.e. outside of the main licensing explanation itself) I'm unsure on - in the spirit of "measure twice and cut commit once".
Subsequent work on this crate has advanced the state of the port from the original commit. | ||
Reviewing the set of upstream LLVM changes after revision `f3598e8fca83ccfb11f58ec7957c229e349765e3` and before the relicensing on 2019-01-19 reveals 41 changes all of which LLVM has relicensing agreements with their authors. | ||
As such, these changes and all changes made to LLVM after the relicensing data are available under the Apache 2 with LLVM Exception license. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't feel particularly strong with regards to that point. We're very confident that everything done here is covered by Apache-2.0 WITH LLVM-exception
and has been done correctly. The timing of this PR going in relative to #1 doesn't change that.
Given that the work has already occurred, it just hasn't been merged into this repo yet, I think what's written is still correct and we can merge the PRs in any order.
Co-authored-by: Eduard-Mihai Burtescu <edy.burt@gmail.com>
cc @eddyb @pnkfelix