From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Shahin Dohan <shahin.dohan@gmail.com>, git@vger.kernel.org
Subject: Re: Bug: Git bash slow after update
Date: Fri, 2 Jun 2023 20:35:13 +0700 [thread overview]
Message-ID: <ZHnwEOa8dlUwDA8E@debian.me> (raw)
In-Reply-To: <CAHsf_F2CgyTWr82htsyg8aiA-WhrKa4zJQUc_wJwF0pfRYR7yQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On Fri, Jun 02, 2023 at 09:42:01AM +0300, 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...
Are there any other significant processes beside git that affect your
system performance?
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-06-02 13:35 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 [this message]
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=ZHnwEOa8dlUwDA8E@debian.me \
--to=bagasdotme@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.