git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: bdavis@saintandreas.org
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Allow git bisect in reverse mode?
Date: Tue, 11 Sep 2018 21:55:39 +0200	[thread overview]
Message-ID: <CACBZZX7EijsVZcwb1BkZdYEzKJbyRWGJNBKXXNRt_i47R0o08w@mail.gmail.com> (raw)
In-Reply-To: <CAMK-fcye+nNyB9pFrp1nQwQC1+sQWMt_4yq2f7svJUiB=ZnnJA@mail.gmail.com>

On Tue, Sep 11, 2018 at 9:54 PM Brad Davis <bdavis@saintandreas.org> wrote:
> I'm currently trying to determine when an issue was fixed in a long
> list of commits.  I attempted to do this by running `git bisect` and
> marking the commit where I knew it was broken as bad, and the tip as
> good, but I got back an error message saying that good revs weren't
> ancestors of bad ones.
>
> I'm currently working around this by mentally reversing the meanings
> of good and bad, but it feels unnatural and error prone to have to say
> `good` when I encounter the failure and `bad` when i don't.
>
> Couldn't git simply do the same thing and internally reverse the
> meaning of good and bad if the bad revision is an ancestor of the
> good?

This feature already exists. See --term-{old,good}=* in the
"git-bisect" manpage.

      reply	other threads:[~2018-09-11 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11 19:52 Allow git bisect in reverse mode? Brad Davis
2018-09-11 19:55 ` Ævar Arnfjörð Bjarmason [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACBZZX7EijsVZcwb1BkZdYEzKJbyRWGJNBKXXNRt_i47R0o08w@mail.gmail.com \
    --to=avarab@gmail.com \
    --cc=bdavis@saintandreas.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).