From: Shahin Dohan <shahin.dohan@gmail.com>
To: git@vger.kernel.org
Subject: Bug: Git bash slow after update
Date: Fri, 2 Jun 2023 09:42:01 +0300 [thread overview]
Message-ID: <CAHsf_F2CgyTWr82htsyg8aiA-WhrKa4zJQUc_wJwF0pfRYR7yQ@mail.gmail.com> (raw)
What did you do before the bug happened? (Steps to reproduce your issue)
Updated Git to 2.41.0
What did you expect to happen? (Expected behavior)
Same performance in Git bash as before
What happened instead? (Actual behavior)
Every operation is significantly slower. CD is slower, git pull is a
lot slower, etc...
What's different between what you expected and what actually happened?
Git bash performance is significantly worse
[System Info]
git version:
git version 2.41.0.windows.1
cpu: x86_64
built from commit: ff94e79c4724635915dbb3d4ba38f6
bb91528260
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 22621
compiler info: gnuc: 13.1
next reply other threads:[~2023-06-02 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 6:42 Shahin Dohan [this message]
2023-06-02 13:35 ` Bug: Git bash slow after update Bagas Sanjaya
2023-06-02 19:11 ` brian m. carlson
2023-06-04 12:43 ` Shahin Dohan
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=CAHsf_F2CgyTWr82htsyg8aiA-WhrKa4zJQUc_wJwF0pfRYR7yQ@mail.gmail.com \
--to=shahin.dohan@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 read-only IMAP folder(s) and NNTP newsgroup(s).