[GitHub] [nuttx] hartmannathan opened a new issue, #8365: tools/checkpatch.sh should check for wrongly set Executable bit

["hartmannathan (via GitHub)" <gi...@apache.org>]

hartmannathan opened a new issue, #8365:
URL: https://github.com/apache/nuttx/issues/8365

   Sometimes source files (e.g., `*.c`, `*.h`, `Make.defs`, etc.) are committed to the repository with the Executable bit unintentionally set (that is, file perms are stored in Git as `100755` instead of `100644`).
   
   `tools/checkpatch.sh` should check for this and warn if the permissions are not set properly.
   
   Files which should be allowed executable bit:
   - `*.sh`
   - `*.py`
   - Not sure about `*.bat` since these are for Windows. Does Executable bit have effect on Windows?
   
   Note: Not recommended to use GNU Find arguments: `find . -type f -executable -print` because this is non-portable. POSIX Find command is: `find . -type f -perm +111 -print`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [nuttx] pkarashchenko closed issue #8365: tools/checkpatch.sh should check for wrongly set Executable bit

["pkarashchenko (via GitHub)" <gi...@apache.org>]

pkarashchenko closed issue #8365: tools/checkpatch.sh should check for wrongly set Executable bit
URL: https://github.com/apache/nuttx/issues/8365


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org