[libnop] create a new port#16471
Merged
ras0219-msft merged 2 commits intomicrosoft:masterfrom Mar 1, 2021
luncliff:port/libnop
Merged
[libnop] create a new port#16471ras0219-msft merged 2 commits intomicrosoft:masterfrom luncliff:port/libnop
ras0219-msft merged 2 commits intomicrosoft:masterfrom
luncliff:port/libnop
Conversation
Contributor
|
LGTM, thanks for the PR! |
19 tasks
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
3 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.
What does your PR fix?
There was no port request for this project.
This package is required by https://github.com/Pytorch/Tensorpipe. The PR will be used for the
tensorpipeport.Which triplets are supported/not supported? Have you updated the CI baseline?
This port is a header-only library, so every triplet must be available.
https://github.com/google/libnop doesn't have
CMakeLists.txt. Simply invokefile(install)to place header files.Does your PR follow the maintainer guide?
"version-date"instead of"version-string", formatted asYYYY-MM-DD.