-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Adding license info #30
Comments
@erickt The Unicode data is only used in tests. Otherwise, all Unicode data comes in the form of finite state machines generated by As for src/utf8.rs, I feel that the comment there is enough. I do not agree that the copyright of src/utf8.rs falls under the copyright of https://bjoern.hoehrmann.de/utf-8/decoder/dfa/. |
erickt
added a commit
to erickt/bstr
that referenced
this issue
Jan 21, 2020
According to this [comment], the unicode data in src/unicode/data is only used by tests, therefore are unnecessary in the published package. [comment]: BurntSushi#30 (comment)
erickt
added a commit
to erickt/bstr
that referenced
this issue
Jan 22, 2020
As a followup to BurntSushi#30, and analogous to this [patch] in rust-lang/regex, This adds the unicode license for the test unicode data in `src/unicode/data`. [patch]: rust-lang/regex#535,
erickt
added a commit
to erickt/bstr
that referenced
this issue
Jan 22, 2020
As a followup to BurntSushi#30, and analogous to this [patch] in rust-lang/regex, this adds the unicode license for the test unicode data in `src/unicode/data`. [patch]: rust-lang/regex#535,
BurntSushi
pushed a commit
that referenced
this issue
Jan 22, 2020
As a followup to #30, and analogous to this rust-lang/regex#535 in rust-lang/regex, this adds the unicode license for the test unicode data in `src/unicode/data`. PR #33
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello @BurntSushi! Would it be possible to add some more license info?
Could you add these licenses to the crate, and reference this in the Cargo.toml / readme? Thanks so much!
The text was updated successfully, but these errors were encountered: