Open
Conversation
Contributor
Author
|
I just noticed this one is still missing, is it because of the merge conflict caused by the other PRs (now fixed) or is there another reason? |
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
1 participant
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.
This allows a configuration to make custom patches to TensorFlow or to Bazel. These patches can be configured by providing their paths inside the
TF_PATCHandBAZEL_PATCHvariables (relative to thepatch/tensorfloworpatch/bazeldirectories, respectively). These patches are applied in addition to the ones that would be applied ifTF_PATCHandBAZEL_PATCHwereyes. IfTF_PATCHandBAZEL_PATCHareyes, as in the current configurations, the behavior shall be the same as before this pull request. IfTF_PATCHandBAZEL_PATCHare empty or not configured, the behavior shall be the same as before this pull request and no patches shall be applied.