All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Trygve Aaberge <trygveaa@gmail.com>
Cc: Git Users <git@vger.kernel.org>, Miriam Rubio <mirucam@gmail.com>,
	Jeff King <peff@peff.net>, Pranit Bauva <pranit.bauva@gmail.com>,
	Christian Couder <christian.couder@gmail.com>
Subject: Re: Using --term-* with bisect breaks skip
Date: Mon, 19 Apr 2021 19:50:07 +0700	[thread overview]
Message-ID: <f5368d12-81d9-8591-53f3-44e2e31a89dd@gmail.com> (raw)
In-Reply-To: <20210419083926.GD10839@aaberge.net>

On 19/04/21 15.39, Trygve Aaberge wrote:
> 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.
> 
Seems interesting, git bisect skip only works on good/bad terms but not on
other terms (and not even on old/new)

I saw similar test on t/t6030-bisect-porcelain.sh (hint: find test
that test for skip) , but I don't know whether that test will pass.
I CC'ed Christian Couder for now.

-- 
An old man doll... just what I always wanted! - Clara

  reply	other threads:[~2021-04-19 12:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-18 15:14 Using --term-* with bisect breaks skip Trygve Aaberge
2021-04-19  6:58 ` Bagas Sanjaya
2021-04-19  8:39   ` Trygve Aaberge
2021-04-19 12:50     ` Bagas Sanjaya [this message]
2021-04-19 18:55 ` Junio C Hamano
2021-04-19 19:32   ` Trygve Aaberge
2021-04-20 12:34 ` [PATCH] test: add test for git bisect skip with --term* arguments Bagas Sanjaya
2021-04-20 18:08   ` Junio C Hamano
2021-04-21  4:08 ` [PATCH v2] " Bagas Sanjaya
2021-04-21 17:25   ` Junio C Hamano
2021-04-22  5:16     ` Bagas Sanjaya

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=f5368d12-81d9-8591-53f3-44e2e31a89dd@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mirucam@gmail.com \
    --cc=peff@peff.net \
    --cc=pranit.bauva@gmail.com \
    --cc=trygveaa@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.