From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: git source files with rw permissions
Date: Thu, 26 Jan 2023 08:07:11 -0800 [thread overview]
Message-ID: <3de4cbc2198105bcbc09ee355cd69a8b8756b89c.camel@perches.com> (raw)
In-Reply-To: <CA+55aFw=EQyJv52LjUje8ExMeX99u=8zzPsQAFv2MZ_N4V=Kog@mail.gmail.com>
On Sat, 2018-04-07 at 13:36 -0700, Linus Torvalds wrote:
> On Thu, Apr 5, 2018 at 5:53 PM, Joe Perches <joe@perches.com> wrote:
> > 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}'
>
> A simpler version of this is:
>
> git ls-files -s '*.[chsS]' | grep '^100755'
>
> and then you can use 'cut -f2' if you just want the filenames and do
> the "xargs chmod" thing.
>
> Which I did, and committed, and just pushed out.
Maybe time to do it again. Current tree:
$ git ls-files -s '*.[chsS]' | grep '^100755' | cut -f2 | xargs chmod 0644
$ git diff --stat -p
drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h | 0
sound/soc/codecs/es8326.c | 0
sound/soc/codecs/es8326.h | 0
3 files changed, 0 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h b/drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h
old mode 100755
new mode 100644
diff --git a/sound/soc/codecs/es8326.c b/sound/soc/codecs/es8326.c
old mode 100755
new mode 100644
diff --git a/sound/soc/codecs/es8326.h b/sound/soc/codecs/es8326.h
old mode 100755
new mode 100644
next prev parent reply other threads:[~2023-01-26 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 0:53 Joe Perches
2018-04-07 20:36 ` Linus Torvalds
2023-01-26 16:07 ` Joe Perches [this message]
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=3de4cbc2198105bcbc09ee355cd69a8b8756b89c.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
Powered by JetHome