Removing executable bit from non-executable files. #1315
Merged
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.
@tseaver I promise I'm not crazy, I originally noticed that the
.proto
files were executable when moving things around forv1beta3
datastore changes.@stephenplusplus @callmehiphop Any idea why the docs resources (which were likely just copied from
gcloud-node
) have the executable bits set? Should I leave them in place?Can verify which files had the bit set with:
After this change it leaves
which all should be executable. We could probably also make our system test runner executable if we felt we needed it.