Skip to content
This repository has been archived by the owner on Nov 6, 2022. It is now read-only.

Update license boilerplate. #390

Merged
merged 1 commit into from
Oct 2, 2017
Merged

Update license boilerplate. #390

merged 1 commit into from
Oct 2, 2017

Conversation

bnoordhuis
Copy link
Member

The boilerplate included attribution to NGINX that created confusion
because NGINX is distributed under a different license (BSD, not MIT.)

To the best of everyone's knowledge, no actual NGINX code remains.
Remove the attribution to clear up the confusion.

Refs: #389

indutny

This comment was marked as off-topic.

@andrew-aladev
Copy link

Sorry, could I ask an offtopic question here? master last change is in 2016 year. Is http-parser repo abandoned?

@indutny
Copy link
Member

indutny commented Oct 1, 2017

@andrew-aladev it is not. No new changes doesn't mean being abandoned.

@andrew-aladev
Copy link

@indutny, Hello. We have here a trivial pull request and nobody wants to merge it. I saw a big amount of good pull requests. For example "Various optimizations". Could you notify project's authors somehow?

The boilerplate included attribution to NGINX that created confusion
because NGINX is distributed under a different license (BSD, not MIT.)

To the best of everyone's knowledge, no actual NGINX code remains.
Remove the attribution to clear up the confusion.

Fixes: nodejs#389
PR-URL: nodejs#390
Reviewed-By: Fedor Indutny <[email protected]>
@bnoordhuis bnoordhuis closed this Oct 2, 2017
@bnoordhuis bnoordhuis deleted the fix389 branch October 2, 2017 09:42
@bnoordhuis bnoordhuis merged commit 89279ab into nodejs:master Oct 2, 2017
ploxiln pushed a commit to ploxiln/http-parser that referenced this pull request Mar 20, 2018
The boilerplate included attribution to NGINX that created confusion
because NGINX is distributed under a different license (BSD, not MIT.)

To the best of everyone's knowledge, no actual NGINX code remains.
Remove the attribution to clear up the confusion.

Fixes: nodejs#389
PR-URL: nodejs#390
Reviewed-By: Fedor Indutny <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants