Re: git-bisect behaves differently when started in equivalent ways
- From
Christian Couder <christian.couder@gmail.com>
- Date
- Apr 13, 2022, 08:37 UTC
- Message-ID
- <CAP8UFD3zZuik9VkrTLivOTjK5GWJ1kEO3hNFN-18t12OFq7Org@mail.gmail.com>
- In-Reply-To
- <878rsbof6v.fsf@drac>
Hi,
On Tue, Apr 12, 2022 at 9:51 PM Christoph Groth <christoph@grothesque.org> wrote:
> I found a puzzling behavior with git-bisect for which I was unable to > find any explanation. Since this might be a bug, I report it here.
Thanks for reporting this strange behavior.
Unfortunately when trying to reproduce, I don't get "f5bba2a7147ef8a6980ff043e93dd038c14bb9bc was both good and bad" like you, but the expected:
Bisecting: 2606 revisions left to test after this (roughly 11 steps) [b335cf582f4a789b725cc37822d6eed42c8d9e71] add test and fix space
You are using Git 2.30.2 which is one year old. Could you try with a more recent version like 2.35.1?
Best, Christian.