From: Calvin Taylor <coolcatt@gmail.com>
To: git@vger.kernel.org
Subject: Bug Report: git ls-files -d
Date: Mon, 27 Sep 2021 10:36:24 -0300 [thread overview]
Message-ID: <CAP9BFHVdg_BWZ2wvdv8t-mN3WKjW4fA+v2181WRYQGsrgmvKmA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 32 bytes --]
--
Calvin Taylor
506 260-2866
[-- Attachment #2: git-bugreport-2021-09-27-0939.txt --]
[-- Type: text/plain, Size: 2001 bytes --]
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
have macos and I have some commands possibly remapped like gsed, gfind to sed, find
What did you expect to happen? (Expected behavior)
git ls-files -d to show deleted files in my repository
What happened instead? (Actual behavior)
nothing is shown, I enabled GIT_TRACE=1, and started bash incase oh-my-zsh might have been interfereing, and got similar results
$ git ls-files -d
09:42:47.692880 exec-cmd.c:139 trace: resolved executable path from Darwin stack: /Library/Developer/CommandLineTools/usr/bin/git
09:42:47.693591 exec-cmd.c:238 trace: resolved executable dir: /Library/Developer/CommandLineTools/usr/bin
09:42:47.695053 git.c:444 trace: built-in: git ls-files -d
09:42:47.764089 exec-cmd.c:139 trace: resolved executable path from Darwin stack: /Library/Developer/CommandLineTools/usr/bin/git
09:42:47.764921 exec-cmd.c:238 trace: resolved executable dir: /Library/Developer/CommandLineTools/usr/bin
09:42:47.765919 git.c:444 trace: built-in: git config --get oh-my-zsh.hide-dirty
What's different between what you expected and what actually happened?
I have several directories I'd like to delete temporarily so I can simplify and study build processes
Anything else you want to add:
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.30.1 (Apple Git-130)
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Darwin 20.6.0 Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:21 PDT 2021; root:xnu-7195.141.6~3/RELEASE_X86_64 x86_64
compiler info: clang: 12.0.5 (clang-1205.0.22.6)
libc info: no libc information available
$SHELL (typically, interactive shell): /bin/zsh
[Enabled Hooks]
next reply other threads:[~2021-09-27 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 13:36 Calvin Taylor [this message]
2021-09-27 21:21 ` Bug Report: git ls-files -d Junio C Hamano
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=CAP9BFHVdg_BWZ2wvdv8t-mN3WKjW4fA+v2181WRYQGsrgmvKmA@mail.gmail.com \
--to=coolcatt@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).