git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: feature request - telling git bisect to skip, from inside a commit

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 28, 2011, 16:51 UTC
Message-ID
<7vipv31943.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20110328163153.GA18774@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 5 quoted lines
> That could work, though I would spell it as a pseudo-header:
>
>   Bisect: Skip
>
> at the end of each commit.

I think that is a saner approach, and further say it would be much saner to make that token something like

    Broken: does not build

A commit may or may not build, a build product may work in some areas just fine and may have known bugs in some other areas, depending on what kind of breakage you are interested in. You might even be looking for a change that fixed a bug for cherry picking. In short, "Bisect: Skip" is too broad a brush, and does not convey enough information.

And then teach the script you give to "bisect run" to grep for that "^Broken: " pattern to answer with exit 125 (cannot test), and you are done.

Previous: Jeff KingNext: Jim Cromie
Message 4 of 6 in “feature request - telling git bisect to skip, from inside a commit”
  1. Jim CromieMar 26, 2011
  2. Christian CouderMar 28, 2011
  3. Jeff KingMar 28, 2011
  4. Junio C HamanoMar 28, 2011
  5. Jim CromieMar 29, 2011
  6. Jeff KingMar 29, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.