git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: git@vger.kernel.org
Subject: git bisect fails to handle annotated tags
Date: Tue, 16 Mar 2021 14:05:51 +0100	[thread overview]
Message-ID: <878s6nz1sg.fsf@igel.home> (raw)

$ git --version
git version 2.31.0
$ git bisect start
$ git bisect good v2.30.0
$ git bisect bad v2.31.0
3e90d4b58f3819cfd58ac61cb8668e83d3ea0563 was both good and bad
$ git bisect log
git bisect start
# good: [71ca53e8125e36efbda17293c50027d31681a41f] Git 2.30
git bisect good 2d9685d47a7e516281aa093bf0cddc8aafa72448
# bad: [a5828ae6b52137b913b978e16cd2334482eb4c1f] Git 2.31
git bisect bad 3e90d4b58f3819cfd58ac61cb8668e83d3ea0563
$ git bisect start
Already on 'master'
Your branch is up to date with 'origin/master'.
$ git bisect good v2.30.0^{}
$ git bisect bad v2.31.0^{}
Bisecting: 453 revisions left to test after this (roughly 9 steps)
[41abfe15d95ede4c2a047180a6062eac23d8f7d6] maintenance: add pack-refs task
$ git bisect log
git bisect start
# good: [71ca53e8125e36efbda17293c50027d31681a41f] Git 2.30
git bisect good 71ca53e8125e36efbda17293c50027d31681a41f
# bad: [a5828ae6b52137b913b978e16cd2334482eb4c1f] Git 2.31
git bisect bad a5828ae6b52137b913b978e16cd2334482eb4c1f

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

             reply	other threads:[~2021-03-16 13:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 13:05 Andreas Schwab [this message]
2021-03-16 14:53 ` git bisect fails to handle annotated tags Jeff King
2021-03-16 15:15   ` [PATCH] bisect: peel annotated tags to commits Jeff King
2021-03-17  8:23     ` Bagas Sanjaya
2021-03-17 18:24     ` Junio C Hamano

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=878s6nz1sg.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=git@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).