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

Re: [PATCH] bisect: Store first bad commit as comment in log file

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 22, 2013, 21:13 UTC
Message-ID
<7vr4i2nuar.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130422210229.GE5650@pvv.ntnu.no>
Torstein Hegge <hegge@resisty.net> writes:
> I took another look at this. I wasn't able to come up with anything
> useful for the "The merge base $rev is bad" case, but for the "only
> skipped commits left to test" case one could do something like this.

We skipped them because we can gain _no_ information from testing these commits. They are not even "possibly bad", but are "unknown".

So it feels to me that by definition listing them would not be useful. What am I missing?

Previous: Torstein HeggeNext: Torstein Hegge
Message 6 of 11 in “bisect: Store first bad commit as comment in log file”
  1. bisect: Store first bad commit as comment in log fileTorstein Hegge, Apr 13, 2013
  2. Christian CouderApr 15, 2013
  3. Torstein HeggeApr 15, 2013
  4. Junio C HamanoApr 15, 2013
  5. Torstein HeggeApr 22, 2013
  6. Junio C HamanoApr 22, 2013
  7. Torstein HeggeApr 22, 2013
  8. Junio C HamanoApr 22, 2013
  9. Christian CouderApr 25, 2013
  10. bisect: Fix log output for multi-parent skip rangesTorstein Hegge, May 22, 2013
  11. Junio C HamanoApr 15, 2013

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.