From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Shahin Dohan <shahin.dohan@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bug: Git bash slow after update
Date: Fri, 2 Jun 2023 19:11:43 +0000 [thread overview]
Message-ID: <ZHo+742ova7QTAe1@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <CAHsf_F2CgyTWr82htsyg8aiA-WhrKa4zJQUc_wJwF0pfRYR7yQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
On 2023-06-02 at 06:42:01, Shahin Dohan wrote:
> 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
The Git project doesn't distribute any binaries at all. If you're using
Git for Windows and seeing problems that are in Git Bash and don't
involve Git (e.g., slowness in the shell with cd), then you'll probably
want to report it to https://github.com/git-for-windows/git/issues/
after searching for any existing issues.
I will also mention that you'll also want to indicate in your report to
the Git for Windows project if downgrading again solves the problem
(which you should try) and if you have any sort of non-default
antivirus, firewall, or monitoring software, since those can affect the
performance of programs on Windows.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2023-06-02 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 6:42 Bug: Git bash slow after update Shahin Dohan
2023-06-02 13:35 ` Bagas Sanjaya
2023-06-02 19:11 ` brian m. carlson [this message]
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=ZHo+742ova7QTAe1@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=shahin.dohan@gmail.com \
/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).