From: Shahin Dohan <shahin.dohan@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Shahin Dohan <shahin.dohan@gmail.com>,
git@vger.kernel.org
Subject: Re: Bug: Git bash slow after update
Date: Sun, 4 Jun 2023 15:43:36 +0300 [thread overview]
Message-ID: <CAHsf_F3m8U+gPSVk8wMmF6ozEW0YgMUQ9qbYBAE+J_FmeAge0Q@mail.gmail.com> (raw)
In-Reply-To: <ZHo+742ova7QTAe1@tapette.crustytoothpaste.net>
Hi Brian & Bagas,
Thanks for your replies, no other processes affect performance and yes
the issue seems to be in Git Bash for Windows rather than Git itself,
I thought it came from you guys as well :)
Apologies for the late response, could not send plain text emails from mobile.
I'll report this to Git for Windows project!
Thanks,
Shahin
On Fri, Jun 2, 2023 at 10:11 PM brian m. carlson
<sandals@crustytoothpaste.net> wrote:
>
> 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
prev parent reply other threads:[~2023-06-04 12:43 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
2023-06-04 12:43 ` Shahin Dohan [this message]
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_F3m8U+gPSVk8wMmF6ozEW0YgMUQ9qbYBAE+J_FmeAge0Q@mail.gmail.com \
--to=shahin.dohan@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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).