git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: git@vger.kernel.org
Cc: Josef Bacik <josef@redhat.com>
Subject: [RFE] allow git bisect to figure out in which revision a bug was fixed
Date: Tue, 21 Jul 2009 16:16:50 -0400	[thread overview]
Message-ID: <x49ocrdokp9.fsf@segfault.boston.devel.redhat.com> (raw)

Hi,

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?

Thanks,
Jeff

             reply	other threads:[~2009-07-21 20:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 20:16 Jeff Moyer [this message]
2009-07-21 20:24 ` [RFE] allow git bisect to figure out in which revision a bug was fixed Junio C Hamano
2009-07-21 20:28   ` Josef Bacik
2009-07-21 20:34     ` Jeff Moyer
2009-07-21 20:40     ` Junio C Hamano
2009-07-21 20:45       ` Jeff Moyer
2009-07-22  0:35       ` Nicolas Pitre
2009-07-22  1:08         ` Junio C Hamano
2009-07-22  1:20           ` Nicolas Pitre
2009-07-22  2:41             ` Junio C Hamano

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x49ocrdokp9.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=git@vger.kernel.org \
    --cc=josef@redhat.com \
    /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. 
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 NNTP newsgroup(s).