Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
-rwxrwxr-x 1 www-data users 102 Nov 16 20:01 persistent_login.info
-rw-rw-r-- 1 www-data users 5.9K Nov 16 20:01 persistent_login.install
-rw-rw-r-- 1 www-data users 22K Nov 16 20:01 persistent_login.module
-rw-rw-r-- 1 www-data users 7.4K Nov 16 20:01 persistent_login.pages.inc
-rw-rw-r-- 1 www-data users 3.6K Nov 16 20:01 CHANGELOG.txt
-rwxrwxr-x 1 www-data users 2.8K Nov 16 20:01 README.txt
http://drupalcode.org/project/persistent_login.git/tree/refs/heads/6.x-1.x
The executable by all permissions seems unnecessary for persistent_login.info and README.txt. What is the best practice here? I couldn't quickly find a reference in the drupal module dev documentation.
Comments
Comment #0.0
dooug CreditAttribution: dooug commentedUpdated issue summary.
Comment #1
gappleI couldn't find a reference for a best practice either, but execute permission is certainly unnecessary.
I'm guessing it most likely occurred to due to a commit from a windows machine.
Fixed in commits:
6.x-1.x: 56f04b1e03c632dc4762f9c57205ee69cc7001aa
7.x-1.x: 9731ba80b5bccca1a7a46be02aef2d8606926b59
Comment #2.0
(not verified) CreditAttribution: commentedUpdated issue summary.