From: Alejandro Colomar <alx+git@kernel.org>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: git@vger.kernel.org, Andy Shevchenko <andy@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: git-ls-files(1) avoiding symlinks
Date: Fri, 6 Nov 2026 15:45:08 +0100 [thread overview]
Message-ID: <au3lu4jYwZ5hBZSy@devuan> (raw)
In-Reply-To: <CALnO6CB-b2XuvwkQ9pJp5ENuc12oGMdgbcwz1VKD_i3KWfKuHA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
Hi Ben,
> Date: 2026-11-06 09:15:22-0500
> From: "D. Ben Knoble" <ben.knoble@gmail.com>
>
[...]
> > A problem with git-ls-files(1) is that it doesn't have a way to filter
> > files by type. That is, it will list symlinks, which will affect the
> > search. With find(1), I can control that with '-type f', which makes
> > sure I only search in regular files. I'd like to have some feature in
> > git-ls-files(1) that allows me to print files of the specified type.
> > Since git(1) knows the type of the files, this should be doable without
> > much overhead, right?
>
> Perhaps something with "git ls-files --format='%(objectmode) %(path)'
> -z"? Of course, your examples already omit -z, so if you can assume
> that it might be simpler.
Hmmm, that could work. Thanks!
$ git ls-files --format='%(objectmode) %(path)' \
| grep -v ^120000 \
| sed 's/^.* //' \
| grep '\.[ch]$' \
| xargs grepc creat;
With -z it becomes a bit tedious:
$ git ls-files -z --format='%(objectmode) %(path)' \
| grep -zv ^120000 \
| sed -z 's/^.* //' \
| grep -z '\.[ch]$' \
| xargs -0 grepc creat;
But, indeed, I don't care about files with spaces often, because I don't
create them in my stuff.
I expect git-ls-files(1) could make this much simpler, though:
$ git ls-files --type f \
| grep '\.[ch]$' \
| xargs grepc creat;
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-11-06 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 13:35 git-ls-files(1) avoiding symlinks Alejandro Colomar
2026-11-06 14:15 ` D. Ben Knoble
2026-11-06 14:45 ` Alejandro Colomar [this message]
[not found] ` <AE63992D-7BEA-413D-A372-78708CFA8F6F@gmail.com>
2026-11-06 19:36 ` Alejandro Colomar
2026-11-06 20:16 ` Junio C Hamano
2026-11-06 21:06 ` Alejandro Colomar
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=au3lu4jYwZ5hBZSy@devuan \
--to=alx+git@kernel.org \
--cc=andy@kernel.org \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=krzk@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