Removing superflous includes for javatests directory.
#325
Conversation
This file contains 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
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=60&v=4){kind=small}
copybara-service
bot
force-pushed
the
test_654622410
branch
4 times, most recently
from
2338cec to
48af150
Compare
These were causing numerous unused include warnings but also can cause some difficulties getting the topology of build includes right which actually does matter for generating release headers, and, in particular matters for the proxy definitions. This CL should not have any effect (no tests are change). PiperOrigin-RevId: 654824989
copybara-service
bot
force-pushed
the
test_654622410
branch
from
48af150 to
89f1760
Compare
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.
Removing superflous includes for
javatestsdirectory.These were causing numerous unused include warnings but also can cause some difficulties getting the topology of build includes right which actually does matter for generating release headers, and, in particular matters for the proxy definitions.
This CL should not have any effect (no tests are change).