Clarify hash and digest licensing obligations - #434
Merged
Merged
Conversation
Signed-off-by: helly25 <6420169+helly25@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clarify that the default hash and digest libraries do not remove mbo's own Apache-2.0 requirements. They introduce no additional third-party requirements; only the optional extra-hash target adds MIT and BSD notice obligations.
AG;DR
//mbo/hash:hash_extra_cc.Validation:
pre-commit run --files README.mdSynchronized with main after release-site PR #433 merged because GitHub rejected the prior required-check context. The licensing clarification and release-site documentation are both preserved; CI is validating the new pushed head.