You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to find the compiled example binaries by searching for executables and was surprised to see lots of the files in the source are executable (see below for a full list).
From a fresh clone you can run find . -type f -perm +0111 | grep -v .git to get a list of executable files in the tree. README.md is one of them:
$ ls -lah README.md
-rwxr-xr-x 1 andy andy 14K 9 Mar 13:12 README.md
GitHub shows the same:
Is there a reason for it? If not, do you want a small PR to drop the executable permission for non-executable files? Otherwise, feel free to close this issue.
Click to expand full list of executable files in source tree
Almost all of the list of unnecessary executable files are coming from external library dependencies...so there is really nothing we can do there...except to complain to them.
As for the MoltenVK files themselves (such as the README.md you noted)...this has been fixed in PR #98.
I was trying to find the compiled example binaries by searching for executables and was surprised to see lots of the files in the source are executable (see below for a full list).
From a fresh clone you can run
find . -type f -perm +0111 | grep -v .git
to get a list of executable files in the tree. README.md is one of them:GitHub shows the same:
Is there a reason for it? If not, do you want a small PR to drop the executable permission for non-executable files? Otherwise, feel free to close this issue.
Click to expand full list of executable files in source tree
The text was updated successfully, but these errors were encountered: