git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Haller <lists@haller-berlin.de>
Cc: Olliver Schinagl <oliver@schinagl.nl>,  git@vger.kernel.org
Subject: Re: Allow git bisect to auto-skip
Date: Sat, 23 Mar 2024 11:43:03 -0700	[thread overview]
Message-ID: <xmqqle68x008.fsf@gitster.g> (raw)
In-Reply-To: <01e09c64-4d62-406d-85fe-9fb77939cf63@haller-berlin.de> (Stefan Haller's message of "Sat, 23 Mar 2024 14:51:21 +0100")

Stefan Haller <lists@haller-berlin.de> writes:

> On 22.03.24 23:31, Junio C Hamano wrote:
>> It often is discovered that a commit
>> breaks bisection after the fact and it is not feasible to rebase
>> all the history after the commit.
>
> This reminds me of a similar problem with git blame, for which we have
> the blame.ignoreRevsFile config to work around it. Couldn't there be a
> similar mechanism for bisect, e.g. bisect.skipRevsFile?

A Very good point.  If a breakage of a commit is "this does not even
build" kind of breakage, such a mechanism would be an excellent fit.

But if a breakage is "only this particular test fails and we know
the reason why it fails has nothing to do with the bug we are
chasing", then compiling such a fixed list of commits, or pointing
at such a list with a configuration variable, would not work very
well, I am afraid.

Thanks.


  reply	other threads:[~2024-03-23 18:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 22:18 Allow git bisect to auto-skip Olliver Schinagl
2024-03-22 22:31 ` Junio C Hamano
2024-03-23  1:59   ` Olliver Schinagl
2024-03-23 13:51   ` Stefan Haller
2024-03-23 18:43     ` Junio C Hamano [this message]
2024-03-23 20:51       ` Olliver Schinagl
2024-03-24  7:47         ` Olliver Schinagl
2024-03-24 10:16       ` Stefan Haller
2024-03-24 14:29         ` Christian Couder
2024-03-24 16:04           ` rsbecker
2024-03-24 18:34           ` Junio C Hamano
2024-03-27 18:33             ` Olliver Schinagl
2024-03-27 19:24               ` Junio C Hamano
2024-03-28  8:01                 ` Olliver Schinagl

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=xmqqle68x008.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=lists@haller-berlin.de \
    --cc=oliver@schinagl.nl \
    /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).