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

Re: [RFE] allow git bisect to figure out in which revision a bug was fixed

From
Nicolas Pitre <nico@cam.org>
Date
Jul 22, 2009, 01:20 UTC
Message-ID
<alpine.LFD.2.00.0907212118550.30629@xanadu.home>
In-Reply-To
<7v4ot5zfqe.fsf@alter.siamese.dyndns.org>
On Tue, 21 Jul 2009, Junio C Hamano wrote:
Show 6 quoted lines
> Nicolas Pitre <nico@cam.org> writes:
> 
> > Why not simply automatically inverting the meaning of good and
> > bad based on which commit is the ancestor of the other initially?
> 
> Because neither may be an ancestor of the other?
In most cases it has to be, no?
Nicolas
Previous: Junio C HamanoNext: Junio C Hamano
Message 9 of 10 in “[RFE] allow git bisect to figure out in which revision a bug was fixed”
  1. Jeff MoyerJul 21, 2009
  2. Junio C HamanoJul 21, 2009
  3. Josef BacikJul 21, 2009
  4. Jeff MoyerJul 21, 2009
  5. Junio C HamanoJul 21, 2009
  6. Jeff MoyerJul 21, 2009
  7. Nicolas PitreJul 22, 2009
  8. Junio C HamanoJul 22, 2009
  9. Nicolas PitreJul 22, 2009
  10. Junio C HamanoJul 22, 2009

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.