mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Stuart MacDonald" <stuartm@connecttech.com>
Cc: "'Paolo Ornati'" <ornati@fastwebnet.it>, <linux-kernel@vger.kernel.org>
Subject: Re: Alternative to 'git bisect visualize'?
Date: Tue, 10 Apr 2007 13:00:25 -0700	[thread overview]
Message-ID: <20070410130025.b16b5f7b.randy.dunlap@oracle.com> (raw)
In-Reply-To: <05ad01c77ba8$cd753040$294b82ce@stuartm>

On Tue, 10 Apr 2007 15:45:33 -0400 Stuart MacDonald wrote:

> From: Paolo Ornati [mailto:ornati@fastwebnet.it] 
> > I think this should work:
> > 
> > 1) look at "git-bisect log" and take the last good/bad pair
> > 
> > 2) "cat .git/refs/heads/bisect" to see where you are now
> > 
> > 3) git-log --pretty=oneline GOOD..BAD
> > 
> > 4) search for the current commit (found in #2) with "/CURRENT_COMMIT",
> > now move around and choose another commit to test
> > 
> > 5) git-reset --hard COMMIT_TO_TEST
> 
> That is exactly what I needed, many many thanks. I have moved off the
> broken area of commits and am back into bisecting.
> 
> Where would be the appropriate place to submit this as a feature
> request, to complement "git bisect visualize"; git, LKML or somewhere
> else? I'm picturing an ncurses/menuconfig-style app.
> 
> ..Stu

see http://git.or.cz/, this section:  Community and Development


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2007-04-10 19:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 21:10 Stuart MacDonald
2007-04-10  8:03 ` Paolo Ornati
2007-04-10 19:45   ` Stuart MacDonald
2007-04-10 20:00     ` Randy Dunlap [this message]
2007-04-10 20:04       ` Stuart MacDonald

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=20070410130025.b16b5f7b.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ornati@fastwebnet.it \
    --cc=stuartm@connecttech.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
Powered by JetHome