Using --term-* with bisect breaks skip · Trygve Aaberge <hidden> · 2021-04-18
Re: Using --term-* with bisect breaks skip · Bagas Sanjaya <hidden> · 2021-04-19
Re: Using --term-* with bisect breaks skip · Trygve Aaberge <hidden> · 2021-04-19
Re: Using --term-* with bisect breaks skip · Bagas Sanjaya <hidden> · 2021-04-19
[PATCH] test: add test for git bisect skip with --term* arguments · Bagas Sanjaya <hidden> · 2021-04-20
[PATCH v2] test: add test for git bisect skip with --term* arguments · Bagas Sanjaya <hidden> · 2021-04-21

Re: Using --term-* with bisect breaks skip

From: Trygve Aaberge <hidden>
Date: 2021-04-19 08:39:34

On Mon, Apr 19, 2021 at 13:58:20 +0700, Bagas Sanjaya wrote:

The issue still persists without --term-* options on my computer.

To reproduce in git.git:
  1. git bisect start
  2. git bisect new v2.31.0
  3. git bisect old v2.30.0
  4. git bisect skip

Right, the issue persists with those commands here too. So it apparently
happens as long as you don't use good/bad, but with good/bad it works as
expected.

-- 
Trygve Aaberge

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help