Vijay Raghavan Aravamudhan <avijayr@xxxxxxxxx> 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
