From: Joe Perches <joe@perches.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: git source files with rw permissions
Date: Thu, 05 Apr 2018 17:53:42 -0700 [thread overview]
Message-ID: <1522976022.11185.53.camel@perches.com> (raw)
Some .c source files have r.x permissions (0755) that
should be updated.
A trivial script on a clean git tree like:
$ git ls-files -- "*.[chsS]" | \
xargs ls -la | \
grep -P "^[^l](?:.{2,2}x|.{5,5}x|.{8,8}x)" | \
awk '{print $9}'
today shows:
drivers/gpu/drm/amd/amdgpu/vce_v4_0.c
drivers/net/ethernet/cadence/macb_ptp.c
It would be good to update those via some script like:
$ git ls-files -- "*.[chsS]" | \
xargs ls -la | \
grep -P
"^[^l](?:.{2,2}x|.{5,5}x|.{8,8}x)" | \
awk '{print $9}' | \
xargs
chmod 644
tmpfile=$(mktemp)
echo "treewide: chmod executable source files
to 0644" > $tmpfile
git commit -s -a -F $tmpfile
rm -f $tmpfile
next reply other threads:[~2018-04-06 0:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 0:53 Joe Perches [this message]
2018-04-07 20:36 ` git source files with rw permissions Linus Torvalds
2023-01-26 16:07 ` Joe Perches
2023-01-26 18:19 ` Linus Torvalds
2023-01-28 4:06 ` Joe Perches
2023-01-28 19:31 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1522976022.11185.53.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox