-
Notifications
You must be signed in to change notification settings - Fork 130
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
Relicense under dual MIT/Apache-2.0 #161
Comments
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
14 similar comments
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license. |
Friendly reminder to @spk @erickt @phildawes : could you please check whether you want to agree to this relicensing? Also, their contributions seem fairly small so maybe we can just go forward with the relicensing. |
I can't remember what my contribution was, but I agree to this relicensing!
Thanks,
Phil
…On Tue, Sep 24, 2019 at 3:21 PM est31 ***@***.***> wrote:
Friendly reminder to @spk <https://github.com/spk> @erickt
<https://github.com/erickt> @phildawes <https://github.com/phildawes> :
could you please check whether you want to agree to this relicensing?
Also, their contributions seem fairly small so maybe we can just go
forward with the relicensing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#161?email_source=notifications&email_token=AAAVLTU42AFKGXSJ267GOTTQLIO5PA5CNFSM4IOWHKXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7ORDFY#issuecomment-534581655>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAVLTWOSRGU6L2WYKDYICTQLIO5PANCNFSM4IOWHKXA>
.
|
This performs the relicensing to MIT/Apache-2.0 as discussed in tiny-http#161 (archived link: http://web.archive.org/web/20191009143715/https://github.com/tiny-http/tiny-http/issues/161) Instead of updating the file headers, I just removed them, as the rustc compiler has done the same: rust-lang/rust#57108
There is a dependency |
Hi, it would be cool to relicense
tiny-http
under the dual license termsMIT OR Apache-2.0
(at the choice of the licensees) that are common in the Rust community.To signify consent, please comment with the following:
Thanks!
Contributor checkoff:
The text was updated successfully, but these errors were encountered: