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
Junio C Hamano <gitster@pobox.com>
Date
Jul 21, 2009, 20:24 UTC
Message-ID
<7vfxcpdbsh.fsf@alter.siamese.dyndns.org>
In-Reply-To
<x49ocrdokp9.fsf@segfault.boston.devel.redhat.com>
Jeff Moyer <jmoyer@redhat.com> writes:
Show 6 quoted lines
> As a distro kernel grunt, I sometimes find myself in the situation of
> having to track down the commit that fixed a given problem so that I can
> backport it to an older kernel.  Sometimes I'm smart enough to figure it
> out myself, other times I'm not.  ;-)  It would be helpful if git bisect
> could help figure out in what commit a bug was fixed as opposed to
> introduced.  Is there any interest in implementing such a feature?
Doesn't that already exist?

You are hunting for an existence of the bug, so any commit that is buggy (with respect to the bug you are interested in) is *GOOD*. The tip of the upstream is *BAD* in that it does not have your favourite bug anymore.

You bisect that history down, and will find the first *BAD* commit.

Now, why is that commit the procedure finds is *BAD*, again? Yup, because it does not have your favourite bug anymore. And why is that so?

Because the commit fixed that bug.
Previous: Jeff MoyerNext: Josef Bacik
Message 2 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.