remove conflicts from opam - mirage generates code with such lower bounds#941
Merged
hannesm merged 1 commit intomirage:masterfrom Nov 8, 2018
Merged
remove conflicts from opam - mirage generates code with such lower bounds#941hannesm merged 1 commit intomirage:masterfrom
hannesm merged 1 commit intomirage:masterfrom
Conversation
Contributor
|
If I understand this correctly, what you're saying is that these "conflicts" only apply to unikernels generated with |
Member
Author
|
Yes, exactly. See #939 (comment) for some explanation why we introduce some upper bounds via conflicts to the |
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
2 participants
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.
no need to keep this information a second time