Re: [PATCH 2/6] status: say when the push branch was rebased cleanly
- From
Harald Nordgren <haraldnordgren@gmail.com>
- Date
- Nov 20, 2026, 19:35 UTC
- Message-ID
- <CAHwyqnXks_cnmLrBxO0E-HkhvMNmnRx8cW9K2Lcyj6tnPUS0hQ@mail.gmail.com>
- In-Reply-To
- <20261120190246.79249-1-aniketgupta3001@gmail.com>
Show 5 quoted lines
> This makes git status slower when the branches have diverged as every
> commit on both sides now needs a patch id. With status.compareBranches =
> @{upstream} @{push} and 3000 commits on both side the status goes from
> 25ms to 150ms. With 10000, it goes from 60ms to 500ms. And with only
> @{upstream} it stays the same.Hmm, that's bad.
> Would it make sense to count without --cherry-mark first and only run > the patch id pass when the two counts are small?
Maybe, but maybe the user experience will be weird if people don't understand why the check is suddenly gone?
Harald