Skip to content
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

Merged
merged 3 commits into from
Jul 18, 2023
Merged

Conversation

wesleywiser
Copy link
Member

Copy link
Member

@eddyb eddyb left a 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".

LICENSE-DETAILS.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
Comment on lines +76 to +78
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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm tempted to merge this PR before #1, such that it attests that everything #1 does is already Apache-2.0 WITH LLVM-exception, but the first sentence here being in the past tense is worrying me in terms of causality. Do you have any preferences/opinions regarding this?

Copy link
Member Author

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.

Cargo.toml Outdated Show resolved Hide resolved
LICENSE-DETAILS.md Outdated Show resolved Hide resolved
wesleywiser and others added 2 commits July 17, 2023 16:36
Co-authored-by: Eduard-Mihai Burtescu <edy.burt@gmail.com>
@eddyb eddyb merged commit c7630d8 into rust-lang:main Jul 18, 2023
@wesleywiser wesleywiser deleted the licensing_info branch July 18, 2023 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants