-
Notifications
You must be signed in to change notification settings - Fork 746
Fix licensing issue #1206
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
Labels
Comments
bors-servo
pushed a commit
that referenced
this issue
Jan 2, 2018
Fix license incompatibility Make issue-816.h compatible with bindgen's 3-clause BSD license. This fixes issue #1206.
bors-servo
pushed a commit
that referenced
this issue
Jan 2, 2018
Fix license incompatibility Make issue-816.h compatible with bindgen's 3-clause BSD license. This fixes issue #1206.
bors-servo
pushed a commit
that referenced
this issue
Jan 2, 2018
Fix license incompatibility Make issue-816.h compatible with bindgen's 3-clause BSD license. This fixes issue #1206.
bors-servo
pushed a commit
that referenced
this issue
Jan 3, 2018
Fix license incompatibility Make issue-816.h compatible with bindgen's 3-clause BSD license. This fixes issue #1206.
bors-servo
pushed a commit
that referenced
this issue
Jan 4, 2018
Fix license incompatibility Make issue-816.h compatible with bindgen's 3-clause BSD license. This fixes issue #1206.
bors-servo
pushed a commit
that referenced
this issue
Jan 4, 2018
Fix license incompatibility Make issue-816.h compatible with bindgen's 3-clause BSD license. This fixes issue #1206.
bors-servo
pushed a commit
that referenced
this issue
Jan 5, 2018
Fix license incompatibility Make issue-816.h compatible with bindgen's 3-clause BSD license. This fixes issue #1206.
Thanks for wrestling with Travis @emilio! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The contents of issue-816.h are covered by a license incompatible with bindgen's 3-clause BSD license. (With the benefit of hindsight, I should have pointed out this problem when I raised issue 816.)
The text was updated successfully, but these errors were encountered: