[qet] [GIT] qet/documentation.git branch KimK/20191111_fix_permissions created. bfad79100f7c2eb9928939fbb1901a15e413df16 |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/qet Archives
]
- To: qet@xxxxxxxxxxxxxxxxxxx
- Subject: [qet] [GIT] qet/documentation.git branch KimK/20191111_fix_permissions created. bfad79100f7c2eb9928939fbb1901a15e413df16
- From: <git@xxxxxxxxxxxxx>
- Date: Mon, 11 Nov 2019 10:28:20 +0100
- Auto-submitted: auto-generated
This is an automated email from git. It was generated because a ref
change was pushed to the "qet/documentation.git" repository.
The branch, KimK/20191111_fix_permissions has been created
at bfad79100f7c2eb9928939fbb1901a15e413df16 (commit)
- Log -----------------------------------------------------------------
commit bfad79100f7c2eb9928939fbb1901a15e413df16
Author: Kim Kirwan <Kim@xxxxxxxxxxxxx>
Date: Mon Nov 11 03:24:44 2019 -0600
Remove Execute Permissions from Non-Executables
Too many "green" files, heh. (No code changes, just permission changes.)
Images (*.jpg, *.gif, *.png, *.svg) don't need execute permission.
Text files (*.txt, *.xml) don't need execute permission.
Web files (*.html, *.css) don't need execute permission.
Odd setup/text files (*.ipe, *.inv, *.rst) don't need execute permission.
I left execute on *.js, *.py, etc., as is, because I don't know whether
they are executed directly or whether something else loads them and
then does the execution, and I didn't need to check. It's close enough
for now that they "might" be executable.
Also, I changed the permissions on the build (output) side, as well as
the permissions on the source (input) side. It would perhaps have been
better to build first and let the source changes propagate over to the
build side, but this way I'll get to see if everything is working OK
when I do eventually build. (Will the wrong permissions come back?)
Signed-off-by: Kim Kirwan <Kim@xxxxxxxxxxxxx>
-----------------------------------------------------------------------
hooks/post-receive
--
qet/documentation.git