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>
Subject: Re: Using --term-* with bisect breaks skip
Date: Mon, 19 Apr 2021 13:58:20 +0700 [thread overview]
Message-ID: <c29ef929-4744-a498-540d-1b7df0afa0a0@gmail.com> (raw)
In-Reply-To: <20210418151459.GC10839@aaberge.net>
On 18/04/21 22.14, Trygve Aaberge wrote:
> What's different between what you expected and what actually happened?
> After running bisect skip, HEAD was still at the same commit as before,
> instead of having changed to a new that I can test. The usual output about
> steps left to test and the new commit was also missing, skip did not output
> anything.
I can reproduce the issue, thanks.
> Anything else you want to add:
> - If I don't provide any --term-* options, skip works as expected.
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
[CC] I'd CCed Miriam and Pranit (who submitted git-bisect in C) and Jeff
for the issue.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-04-19 6:58 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 [this message]
2021-04-19 8:39 ` Trygve Aaberge
2021-04-19 12:50 ` Bagas Sanjaya
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=c29ef929-4744-a498-540d-1b7df0afa0a0@gmail.com \
--to=bagasdotme@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.