From: Sean Allred <allred.sean@gmail.com>
To: Vijay Raghavan Aravamudhan <avijayr@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git status became very slow after upgrading git
Date: Sat, 10 Feb 2024 11:06:20 -0600 [thread overview]
Message-ID: <m05xyw9r92.fsf@epic96565.epic.com> (raw)
In-Reply-To: <CAK7MZG1MeeS5QNPog9oS+MbdKpkDXu61eVOszsC20Q=ik+Ng=g@mail.gmail.com>
Vijay Raghavan Aravamudhan <avijayr@gmail.com> writes:
> What did you do before the bug happened? (Steps to reproduce your issue)
> 1. brew update which pulled in latest version of git
> 2. git status in a repository (without submodules)
>
> What did you expect to happen? (Expected behavior)
> git status should have been fast
>
> What happened instead? (Actual behavior)
> git status takes almost 5s to complete.
Thanks for the report. This isn't a whole lot of information to go on.
At least, I'm not able to reproduce locally with a trivial repository:
git init
echo foo > file
git add file
git commit -mtest
git status
If you're able to reproduce, can you re-run `git status` with tracing
enabled and provide your output?
GIT_TRACE=1 GIT_TRACE_SETUP=1 GIT_TRACE_PERFORMANCE=1 git status
If you can provide reproduction instructions that start with `git init`,
that would also help. It may take some time for you, but it'll take less
time than folks on this list taking shots in the dark :-)
--
Sean Allred
next prev parent reply other threads:[~2024-02-10 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 4:49 git status became very slow after upgrading git Vijay Raghavan Aravamudhan
2024-02-10 17:06 ` Sean Allred [this message]
2024-02-10 18:42 ` Vijay Raghavan Aravamudhan
2024-02-10 19:06 ` Sean Allred
2024-02-10 19:57 ` Vijay Raghavan Aravamudhan
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=m05xyw9r92.fsf@epic96565.epic.com \
--to=allred.sean@gmail.com \
--cc=avijayr@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